Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efb9d8a6255e2eaaa619e203e1e89cd78cafe8e5bcf3857510187a612d1e7661

Tx prefix hash: 357781c067b482854f7ec9c7a597c7df81e4f6a9542df1e96f06f59a5ddc069f
Tx public key: 8d3247f81b185a6e40536cea6a57552afe36de02bf65b972fc25ca8d8116c393
Timestamp: 1721236399 Timestamp [UCT]: 2024-07-17 17:13:19 Age [y:d:h:m:s]: 00:129:14:53:31
Block: 1067814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92741 RingCT/type: yes/0
Extra: 018d3247f81b185a6e40536cea6a57552afe36de02bf65b972fc25ca8d8116c39302110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1dc70ee0ac351c64f2c66a7fefc98ceb663d1779bdea2bc76a7ab2d06d40529 0.600000000000 1538733 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": 1067824, "vin": [ { "gen": { "height": 1067814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1dc70ee0ac351c64f2c66a7fefc98ceb663d1779bdea2bc76a7ab2d06d40529" } } ], "extra": [ 1, 141, 50, 71, 248, 27, 24, 90, 110, 64, 83, 108, 234, 106, 87, 85, 42, 254, 54, 222, 2, 191, 101, 185, 114, 252, 37, 202, 141, 129, 22, 195, 147, 2, 17, 0, 0, 0, 8, 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