Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e4b98732971b7f3cfb835cfba54fc5fbfdb06eb401b1a85275e16be87d417ff

Tx prefix hash: 3554f5a9930cdf31429c2b10f722b7d98d8ebb5ce1ebf2ad6d3a8623e6c3db09
Tx public key: d1feedf87dfbd9cbce3956a6050d6e854dc1ca740310feda27267d64dd05670d
Timestamp: 1674904476 Timestamp [UCT]: 2023-01-28 11:14:36 Age [y:d:h:m:s]: 02:081:23:42:07
Block: 684567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 580231 RingCT/type: yes/0
Extra: 01d1feedf87dfbd9cbce3956a6050d6e854dc1ca740310feda27267d64dd05670d0211000000025029cbac000000000000000000

1 output(s) for total of 3.309369710000 dcy

stealth address amount amount idx
00: f502ebb77c21c4aaf5fbe6da8da6c1d4bb6c2b502c40e7eec0ceca877d1648d6 3.309369710000 1126821 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": 684577, "vin": [ { "gen": { "height": 684567 } } ], "vout": [ { "amount": 3309369710, "target": { "key": "f502ebb77c21c4aaf5fbe6da8da6c1d4bb6c2b502c40e7eec0ceca877d1648d6" } } ], "extra": [ 1, 209, 254, 237, 248, 125, 251, 217, 203, 206, 57, 86, 166, 5, 13, 110, 133, 77, 193, 202, 116, 3, 16, 254, 218, 39, 38, 125, 100, 221, 5, 103, 13, 2, 17, 0, 0, 0, 2, 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