Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7836e8fd9af62b6c4bbddae3e6ae54d8cc6b47c6579b94ab91846eed9f34e36d

Tx prefix hash: 2d5a2e3974fea3c06ed4a6736b1aad9923dd5a8c0b6ffc896ddc1e63e2e7f54c
Tx public key: 6a0eb0d0b01056af48ae2f1c110d9f33089af025e826176b807edb3958109556
Timestamp: 1725761506 Timestamp [UCT]: 2024-09-08 02:11:46 Age [y:d:h:m:s]: 00:216:11:33:04
Block: 1105323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154558 RingCT/type: yes/0
Extra: 016a0eb0d0b01056af48ae2f1c110d9f33089af025e826176b807edb3958109556021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e5b44a9735411f3eb9c9d5aa6794583f884ce9946376e07f3d558d8dc0e5efe 0.600000000000 1582664 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": 1105333, "vin": [ { "gen": { "height": 1105323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e5b44a9735411f3eb9c9d5aa6794583f884ce9946376e07f3d558d8dc0e5efe" } } ], "extra": [ 1, 106, 14, 176, 208, 176, 16, 86, 175, 72, 174, 47, 28, 17, 13, 159, 51, 8, 154, 240, 37, 232, 38, 23, 107, 128, 126, 219, 57, 88, 16, 149, 86, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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