Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 451fc4bf3ece79ba501784e6ecf0ab3398087e484fe50b836499a793cc5203a4

Tx prefix hash: bd0cd3921c14d1d3d250a3f7e88d4611183bf6a5b1dec59c4584f92bf5f00939
Tx public key: 59a5467def03bfa067b3a4338e06f99309074a0ff8da9ee3d8d45cd494591cde
Timestamp: 1675640267 Timestamp [UCT]: 2023-02-05 23:37:47 Age [y:d:h:m:s]: 02:277:05:35:26
Block: 690675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 717467 RingCT/type: yes/0
Extra: 0159a5467def03bfa067b3a4338e06f99309074a0ff8da9ee3d8d45cd494591cde0211000000015029cbac000000000000000000

1 output(s) for total of 3.158689517000 dcy

stealth address amount amount idx
00: cc9c017b5845511eb26af3fe3569f0ffacdd7ce1bf8d48a6fbbb2ac8e5f227a6 3.158689517000 1133409 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": 690685, "vin": [ { "gen": { "height": 690675 } } ], "vout": [ { "amount": 3158689517, "target": { "key": "cc9c017b5845511eb26af3fe3569f0ffacdd7ce1bf8d48a6fbbb2ac8e5f227a6" } } ], "extra": [ 1, 89, 165, 70, 125, 239, 3, 191, 160, 103, 179, 164, 51, 142, 6, 249, 147, 9, 7, 74, 15, 248, 218, 158, 227, 216, 212, 92, 212, 148, 89, 28, 222, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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