Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9be3c502c4db97daaba49c5e83ba110d04790307489c918437a862f89276716

Tx prefix hash: 17288d312089f91eb0897d86f81e39f11b7e071b008eff2c4539e246b6ea8c2a
Tx public key: 195d1dd7b8b8159286ca7a3cb5809bef2d8e73dbfe67dd49b0adb72b38cb4e09
Timestamp: 1704178522 Timestamp [UCT]: 2024-01-02 06:55:22 Age [y:d:h:m:s]: 01:321:02:23:00
Block: 926374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488340 RingCT/type: yes/0
Extra: 01195d1dd7b8b8159286ca7a3cb5809bef2d8e73dbfe67dd49b0adb72b38cb4e090211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d63b3d604e4607ae3b66ceb9ba15b3957030d68ddf04fd40aa6594ab5eca656 0.600000000000 1384156 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": 926384, "vin": [ { "gen": { "height": 926374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d63b3d604e4607ae3b66ceb9ba15b3957030d68ddf04fd40aa6594ab5eca656" } } ], "extra": [ 1, 25, 93, 29, 215, 184, 184, 21, 146, 134, 202, 122, 60, 181, 128, 155, 239, 45, 142, 115, 219, 254, 103, 221, 73, 176, 173, 183, 43, 56, 203, 78, 9, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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