Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0bcbd87ede5e15b09cb065c2d7b0da5c8343e611c3842fb6c1b9664fee07c27

Tx prefix hash: 969ec9507f1b62ecdf1fa2018ec8127d16bdf863c333d73bbe3fed6bbce58418
Tx public key: 6d4f5d3cd2d8a089f16078d95bba74b1c30f32a83cf3b3745fa028a9b1321b17
Timestamp: 1704867172 Timestamp [UCT]: 2024-01-10 06:12:52 Age [y:d:h:m:s]: 01:110:01:28:27
Block: 932081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339793 RingCT/type: yes/0
Extra: 016d4f5d3cd2d8a089f16078d95bba74b1c30f32a83cf3b3745fa028a9b1321b170211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4be1fbd59b7526f830de7cf943472bbd661ba7e175129f2294d99ca17eb22ed 0.600000000000 1390001 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": 932091, "vin": [ { "gen": { "height": 932081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4be1fbd59b7526f830de7cf943472bbd661ba7e175129f2294d99ca17eb22ed" } } ], "extra": [ 1, 109, 79, 93, 60, 210, 216, 160, 137, 241, 96, 120, 217, 91, 186, 116, 177, 195, 15, 50, 168, 60, 243, 179, 116, 95, 160, 40, 169, 177, 50, 27, 23, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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