Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d85797adc9be1032dd1382e95181f963c86a24e84e2d9bfc6d0a49796a43cdb

Tx prefix hash: 3ac507f439356df89442227a60db92d437a1d8308e66ccb7480aad5dc8a4d1b6
Tx public key: db884fe3e004910d5c31424ca40e51607130522631283a7c8e4ce36c9500ae8c
Timestamp: 1741280911 Timestamp [UCT]: 2025-03-06 17:08:31 Age [y:d:h:m:s]: 00:006:00:56:04
Block: 1233525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4330 RingCT/type: yes/0
Extra: 01db884fe3e004910d5c31424ca40e51607130522631283a7c8e4ce36c9500ae8c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34712f98bc84f3b3097c4823919a54f4b0855f6c19eb8b4e09b823d045a7c487 0.600000000000 1720446 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": 1233535, "vin": [ { "gen": { "height": 1233525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34712f98bc84f3b3097c4823919a54f4b0855f6c19eb8b4e09b823d045a7c487" } } ], "extra": [ 1, 219, 136, 79, 227, 224, 4, 145, 13, 92, 49, 66, 76, 164, 14, 81, 96, 113, 48, 82, 38, 49, 40, 58, 124, 142, 76, 227, 108, 149, 0, 174, 140, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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