Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efccd8b4be2557f1c11daf82cffa4c4d13113cc98bfd84da5aaca9715c67f8bc

Tx prefix hash: 10305385972eaa009d70a1bfcdb395fffae0cfbf10b32d16ea126d60d2492268
Tx public key: 35f51f6b728cd916e52e067ab5b25a952cbfa22ca179256231831faae62b22e3
Timestamp: 1704314184 Timestamp [UCT]: 2024-01-03 20:36:24 Age [y:d:h:m:s]: 01:076:15:44:07
Block: 927529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315883 RingCT/type: yes/0
Extra: 0135f51f6b728cd916e52e067ab5b25a952cbfa22ca179256231831faae62b22e3021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5efbc6ba3a8dc0f17d1acd04a9a8fdff09cbe57e837a89d7adc1c14925b61f5b 0.600000000000 1385365 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": 927539, "vin": [ { "gen": { "height": 927529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5efbc6ba3a8dc0f17d1acd04a9a8fdff09cbe57e837a89d7adc1c14925b61f5b" } } ], "extra": [ 1, 53, 245, 31, 107, 114, 140, 217, 22, 229, 46, 6, 122, 181, 178, 90, 149, 44, 191, 162, 44, 161, 121, 37, 98, 49, 131, 31, 170, 230, 43, 34, 227, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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