Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96ddd82a66ffabe161baddb5653adee52138c8ca655a0c1ab859ea4997e7eb68

Tx prefix hash: ff231f9b7c876178bd04c633ac04873feb319aeb07d8e7ef4aa0e4d5d19e227a
Tx public key: b053535eb222e57c01ac7d4a7e186aad5cfe963e6dfed1aca053982409104748
Timestamp: 1578915140 Timestamp [UCT]: 2020-01-13 11:32:20 Age [y:d:h:m:s]: 05:048:14:09:47
Block: 44532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184936 RingCT/type: yes/0
Extra: 01b053535eb222e57c01ac7d4a7e186aad5cfe963e6dfed1aca05398240910474802110000010649b77a3d000000000000000000

1 output(s) for total of 436.966193913000 dcy

stealth address amount amount idx
00: 8c9fd0b709d793defe7cb95da261036b6832ee52f626f9824a02398c2d91daa3 436.966193913000 81063 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": 44542, "vin": [ { "gen": { "height": 44532 } } ], "vout": [ { "amount": 436966193913, "target": { "key": "8c9fd0b709d793defe7cb95da261036b6832ee52f626f9824a02398c2d91daa3" } } ], "extra": [ 1, 176, 83, 83, 94, 178, 34, 229, 124, 1, 172, 125, 74, 126, 24, 106, 173, 92, 254, 150, 62, 109, 254, 209, 172, 160, 83, 152, 36, 9, 16, 71, 72, 2, 17, 0, 0, 1, 6, 73, 183, 122, 61, 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