Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bfc91acd1a56904dd09c393d5c15012c8a257228f00510bbead458dadd09bb6

Tx prefix hash: fd100f1858fbcdf06e9d610c9491d1e5a57a5ab71eb948e7f280fe15e50428f2
Tx public key: 5b11e1142699292b1f076dc66dede1dc467c1f9956fdd10c3a0458f6d13f417d
Timestamp: 1743315021 Timestamp [UCT]: 2025-03-30 06:10:21 Age [y:d:h:m:s]: 00:303:18:55:29
Block: 1250359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214761 RingCT/type: yes/0
Extra: 015b11e1142699292b1f076dc66dede1dc467c1f9956fdd10c3a0458f6d13f417d0211000000031a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 298f939dcf138810efd517a6c4c74a7a43104fb3c748a746b71e47e2880a7fb8 0.600000000000 1737408 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": 1250369, "vin": [ { "gen": { "height": 1250359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "298f939dcf138810efd517a6c4c74a7a43104fb3c748a746b71e47e2880a7fb8" } } ], "extra": [ 1, 91, 17, 225, 20, 38, 153, 41, 43, 31, 7, 109, 198, 109, 237, 225, 220, 70, 124, 31, 153, 86, 253, 209, 12, 58, 4, 88, 246, 209, 63, 65, 125, 2, 17, 0, 0, 0, 3, 26, 151, 4, 3, 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