Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bffe211e22ef10e18e5cf17f58f7e61e4d0b21c49a9b5e4221635ca7993af1e7

Tx prefix hash: 6037553f94c9de59d1ef6f328eb4e1e7ae69cbfeeab677ab91439bdf0149972c
Tx public key: 67ff13e081fd458ba47f48f85d7477a03d671a25b5e62d7599c3042301efdf54
Timestamp: 1750878418 Timestamp [UCT]: 2025-06-25 19:06:58 Age [y:d:h:m:s]: 00:148:17:51:08
Block: 1312686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104272 RingCT/type: yes/0
Extra: 0167ff13e081fd458ba47f48f85d7477a03d671a25b5e62d7599c3042301efdf54021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 086b5fbdf9ddd38dcfe2afa82fce67e26901e6de2bdae20ad8635158bd994e18 0.600000000000 1800321 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": 1312696, "vin": [ { "gen": { "height": 1312686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "086b5fbdf9ddd38dcfe2afa82fce67e26901e6de2bdae20ad8635158bd994e18" } } ], "extra": [ 1, 103, 255, 19, 224, 129, 253, 69, 139, 164, 127, 72, 248, 93, 116, 119, 160, 61, 103, 26, 37, 181, 230, 45, 117, 153, 195, 4, 35, 1, 239, 223, 84, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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