Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb9f5135e86d6e9eef70039a5e072de8874c5829a0e87c9c735338da165239be

Tx prefix hash: dc742a91353aebe0b3acf6dfe114b435ebee89508f07641119fabd62deb3c248
Tx public key: d8fd7c36cf3c8facd2b2c876dc4a46b12c856d33f23c31134723efb38ae5499b
Timestamp: 1747784075 Timestamp [UCT]: 2025-05-20 23:34:35 Age [y:d:h:m:s]: 00:179:04:56:30
Block: 1287369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125770 RingCT/type: yes/0
Extra: 01d8fd7c36cf3c8facd2b2c876dc4a46b12c856d33f23c31134723efb38ae5499b0211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 871c9d372ecda7176a3184f5ee1b3abb265eb95eeb89ce717989fb89105053da 0.600000000000 1774836 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": 1287379, "vin": [ { "gen": { "height": 1287369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "871c9d372ecda7176a3184f5ee1b3abb265eb95eeb89ce717989fb89105053da" } } ], "extra": [ 1, 216, 253, 124, 54, 207, 60, 143, 172, 210, 178, 200, 118, 220, 74, 70, 177, 44, 133, 109, 51, 242, 60, 49, 19, 71, 35, 239, 179, 138, 229, 73, 155, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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