Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c2049d978d3c21bc7bb59322c14e93954db5b8ccbed7938f012a37c9ca77ba1

Tx prefix hash: e77ce3e935ddefdc4d574657e6dc343539be93b2ecd670c2135b9cde36a9e5ed
Tx public key: ad99e22432ac81e80737873b32ec75a531e1e571b902b623376f1fdf65e5cf61
Timestamp: 1703306769 Timestamp [UCT]: 2023-12-23 04:46:09 Age [y:d:h:m:s]: 01:323:13:25:48
Block: 919157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490092 RingCT/type: yes/0
Extra: 01ad99e22432ac81e80737873b32ec75a531e1e571b902b623376f1fdf65e5cf610211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c556cc5f4c8d29cd33d59a186973f76b414af500436fb8025c56199d6ab1428 0.600000000000 1376821 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": 919167, "vin": [ { "gen": { "height": 919157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c556cc5f4c8d29cd33d59a186973f76b414af500436fb8025c56199d6ab1428" } } ], "extra": [ 1, 173, 153, 226, 36, 50, 172, 129, 232, 7, 55, 135, 59, 50, 236, 117, 165, 49, 225, 229, 113, 185, 2, 182, 35, 55, 111, 31, 223, 101, 229, 207, 97, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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