Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7be97f0723ac9dce3831180b20935e290df10d832d48e7ee8a6cc06461d2541b

Tx prefix hash: 5e5c43fae54a165f1f9e641578b0e4a002ffb9ec9afd9e63d729e1a66bc4d992
Tx public key: 081b1d080373c0001e1844367aa37a0cd19971f914d42721a7f5fcbf2ad600fe
Timestamp: 1744723487 Timestamp [UCT]: 2025-04-15 13:24:47 Age [y:d:h:m:s]: 00:029:11:28:08
Block: 1262015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21096 RingCT/type: yes/0
Extra: 01081b1d080373c0001e1844367aa37a0cd19971f914d42721a7f5fcbf2ad600fe021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abe27acad09476d04833863360b4959aa9bd575ae1bd5e35c3f97bfb5cfb9d89 0.600000000000 1749192 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": 1262025, "vin": [ { "gen": { "height": 1262015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abe27acad09476d04833863360b4959aa9bd575ae1bd5e35c3f97bfb5cfb9d89" } } ], "extra": [ 1, 8, 27, 29, 8, 3, 115, 192, 0, 30, 24, 68, 54, 122, 163, 122, 12, 209, 153, 113, 249, 20, 212, 39, 33, 167, 245, 252, 191, 42, 214, 0, 254, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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