Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b41fa97b9aa13e29b944fe0a70c64a399540d7212e08da52ccda07ddd4a36425

Tx prefix hash: a4a5b83848baabc72f2a2a32de405962f089669fde0d15b5f2c450712ee36436
Tx public key: dbf503a5cf6b0b618087c957c499b6e86167ff1fa934a8a4d790b1f336a1060e
Timestamp: 1711804654 Timestamp [UCT]: 2024-03-30 13:17:34 Age [y:d:h:m:s]: 00:270:06:30:47
Block: 989637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193452 RingCT/type: yes/0
Extra: 01dbf503a5cf6b0b618087c957c499b6e86167ff1fa934a8a4d790b1f336a1060e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a9916272521d7677cbbd4b39dfec675d63ad47b0f4ee7ae1d48a9da674bf0d7 0.600000000000 1449953 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": 989647, "vin": [ { "gen": { "height": 989637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a9916272521d7677cbbd4b39dfec675d63ad47b0f4ee7ae1d48a9da674bf0d7" } } ], "extra": [ 1, 219, 245, 3, 165, 207, 107, 11, 97, 128, 135, 201, 87, 196, 153, 182, 232, 97, 103, 255, 31, 169, 52, 168, 164, 215, 144, 177, 243, 54, 161, 6, 14, 2, 17, 0, 0, 0, 4, 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