Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 36972e28e1168136c41b15642dd96b7de0d71c31c8e4e51a0d3bbee33abfc7ef

Tx prefix hash: d3204852cff2ff0c11f8c29adbcc9b335507780c5eb2682f50d04f30e25f2dc8
Tx public key: 32323075849f0c46e309ba9209857bf2b5c98395e4e4fb5588fd5f0006548110
Timestamp: 1710206228 Timestamp [UCT]: 2024-03-12 01:17:08 Age [y:d:h:m:s]: 01:101:08:04:45
Block: 976367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333283 RingCT/type: yes/0
Extra: 0132323075849f0c46e309ba9209857bf2b5c98395e4e4fb5588fd5f00065481100211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6883ba60e7199867958a9f2306d60b5bfc293947df330b0d01661a7c21646e9d 0.600000000000 1436360 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 976377, "vin": [ { "gen": { "height": 976367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6883ba60e7199867958a9f2306d60b5bfc293947df330b0d01661a7c21646e9d" } } ], "extra": [ 1, 50, 50, 48, 117, 132, 159, 12, 70, 227, 9, 186, 146, 9, 133, 123, 242, 181, 201, 131, 149, 228, 228, 251, 85, 136, 253, 95, 0, 6, 84, 129, 16, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8