Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66c75d90b1c83db9aecaff0d224b238ea751384a288251641678814df5f5bfb5

Tx prefix hash: e84cfb8e736ed7e0894e7a3f46f617752569e76a5a09a776e123675e0691cc94
Tx public key: 1d4e5c4c29c84faa99e474b945735d1519fe25061c8a1bf86956bd7f4dc7a84a
Timestamp: 1702697469 Timestamp [UCT]: 2023-12-16 03:31:09 Age [y:d:h:m:s]: 01:152:05:02:06
Block: 914107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369939 RingCT/type: yes/0
Extra: 011d4e5c4c29c84faa99e474b945735d1519fe25061c8a1bf86956bd7f4dc7a84a021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f297ee44f68074666fdb0b7f365c1d1a00a63e19cd255e1fa737c2b75719801 0.600000000000 1371391 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": 914117, "vin": [ { "gen": { "height": 914107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f297ee44f68074666fdb0b7f365c1d1a00a63e19cd255e1fa737c2b75719801" } } ], "extra": [ 1, 29, 78, 92, 76, 41, 200, 79, 170, 153, 228, 116, 185, 69, 115, 93, 21, 25, 254, 37, 6, 28, 138, 27, 248, 105, 86, 189, 127, 77, 199, 168, 74, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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