Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3af6d7dc715e16dcab8793bd17fd7b180398f321e4e375f21d488b1cd6216d1e

Tx prefix hash: 507ca8c82c1f8a4d0853d95a7324f0103829d43256a250028c6219472c64ed57
Tx public key: 671dbbc7cc767a85f02ab267c5a8df2cd390bf1b5b627832d3fd1927410c2252
Timestamp: 1716427301 Timestamp [UCT]: 2024-05-23 01:21:41 Age [y:d:h:m:s]: 01:193:11:34:31
Block: 1027931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396915 RingCT/type: yes/0
Extra: 01671dbbc7cc767a85f02ab267c5a8df2cd390bf1b5b627832d3fd1927410c225202110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20769f770c7a3d9dee67eb3a947aca62ca57a66a6a356510678641f00a07e4e1 0.600000000000 1495814 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": 1027941, "vin": [ { "gen": { "height": 1027931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20769f770c7a3d9dee67eb3a947aca62ca57a66a6a356510678641f00a07e4e1" } } ], "extra": [ 1, 103, 29, 187, 199, 204, 118, 122, 133, 240, 42, 178, 103, 197, 168, 223, 44, 211, 144, 191, 27, 91, 98, 120, 50, 211, 253, 25, 39, 65, 12, 34, 82, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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