Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc8493491491b58ba816c88995ade91729de97b0bf541b0389109d5af4e85783

Tx prefix hash: 640964e83325177ccd2aaf9e1f2b9d09a9c1a03763c4c07429278b1f0288e3ea
Tx public key: 746aaf1c50b2853ebea212fde3b2ba816b2eed975f678356b18d8568b13892b3
Timestamp: 1728986388 Timestamp [UCT]: 2024-10-15 09:59:48 Age [y:d:h:m:s]: 00:100:12:40:22
Block: 1132061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71803 RingCT/type: yes/0
Extra: 01746aaf1c50b2853ebea212fde3b2ba816b2eed975f678356b18d8568b13892b302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 439140ff5367ff3dcfb2ae9738006495f7e8e9872d7fc83f347bda084e1b3602 0.600000000000 1614970 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": 1132071, "vin": [ { "gen": { "height": 1132061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "439140ff5367ff3dcfb2ae9738006495f7e8e9872d7fc83f347bda084e1b3602" } } ], "extra": [ 1, 116, 106, 175, 28, 80, 178, 133, 62, 190, 162, 18, 253, 227, 178, 186, 129, 107, 46, 237, 151, 95, 103, 131, 86, 177, 141, 133, 104, 177, 56, 146, 179, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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