Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cd9101bc1fbd743f46028d85be9343e1bf2f5f3139acce45fd6916de0fbad16

Tx prefix hash: 7a93b2a310935959fef7ddea5ebdb96a6106906b0dc7cc1d034cb316b70b72aa
Tx public key: 3695942cab9bb1fae7290e30a41e6c38e024d4fd216317db8c623129995349c9
Timestamp: 1703291029 Timestamp [UCT]: 2023-12-23 00:23:49 Age [y:d:h:m:s]: 01:317:05:26:27
Block: 919029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485558 RingCT/type: yes/0
Extra: 013695942cab9bb1fae7290e30a41e6c38e024d4fd216317db8c623129995349c90211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 040a1199f43eeba8711ecd7a45d936612647047c3618f26497c708510ff9b7c3 0.600000000000 1376693 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": 919039, "vin": [ { "gen": { "height": 919029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "040a1199f43eeba8711ecd7a45d936612647047c3618f26497c708510ff9b7c3" } } ], "extra": [ 1, 54, 149, 148, 44, 171, 155, 177, 250, 231, 41, 14, 48, 164, 30, 108, 56, 224, 36, 212, 253, 33, 99, 23, 219, 140, 98, 49, 41, 153, 83, 73, 201, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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