Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8a5b425d4927e3159ff8f948671762e8c75faa20548f0ef102dcf90c7708e75

Tx prefix hash: eea2027b2a482a369a5d3f829acfd927b68b41eb5d9d3e7b0597017db9a683bc
Tx public key: 591b86b94e1c91e5f684c05c2613dc9b865242f9be88f3a47472eb4da73bdf96
Timestamp: 1577961699 Timestamp [UCT]: 2020-01-02 10:41:39 Age [y:d:h:m:s]: 04:308:11:00:44
Block: 37160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109479 RingCT/type: yes/0
Extra: 01591b86b94e1c91e5f684c05c2613dc9b865242f9be88f3a47472eb4da73bdf960211000000264ac5aa02000000000000000000

1 output(s) for total of 462.247260441000 dcy

stealth address amount amount idx
00: 5b9e3f3f5087ed30019067f74ac8dcc7345ebb82a1a16c09e80e2ba964cb8bf5 462.247260441000 63008 of 0

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": 37170, "vin": [ { "gen": { "height": 37160 } } ], "vout": [ { "amount": 462247260441, "target": { "key": "5b9e3f3f5087ed30019067f74ac8dcc7345ebb82a1a16c09e80e2ba964cb8bf5" } } ], "extra": [ 1, 89, 27, 134, 185, 78, 28, 145, 229, 246, 132, 192, 92, 38, 19, 220, 155, 134, 82, 66, 249, 190, 136, 243, 164, 116, 114, 235, 77, 167, 59, 223, 150, 2, 17, 0, 0, 0, 38, 74, 197, 170, 2, 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