Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b34fe1cae067c965d0507c1aefc54b622116c9158fe30d58a3eb42ffbd19fbfd

Tx prefix hash: 5376875ae626e5b1b140697b9adbce312480a4dc5e9826d9ead5a4b82de15d97
Tx public key: 3d7cfad3d71e586fa349f51980ea32ee0ad73d93ad9a7745de34cafbf4111d9a
Timestamp: 1687648848 Timestamp [UCT]: 2023-06-24 23:20:48 Age [y:d:h:m:s]: 01:228:11:23:00
Block: 789607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424421 RingCT/type: yes/0
Extra: 013d7cfad3d71e586fa349f51980ea32ee0ad73d93ad9a7745de34cafbf4111d9a02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.484924500000 dcy

stealth address amount amount idx
00: 65b2d464eddca8ef4cb399511b0a2f7a22f8916cbd15294d9930ac025b18d92e 1.484924500000 1239844 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": 789617, "vin": [ { "gen": { "height": 789607 } } ], "vout": [ { "amount": 1484924500, "target": { "key": "65b2d464eddca8ef4cb399511b0a2f7a22f8916cbd15294d9930ac025b18d92e" } } ], "extra": [ 1, 61, 124, 250, 211, 215, 30, 88, 111, 163, 73, 245, 25, 128, 234, 50, 238, 10, 215, 61, 147, 173, 154, 119, 69, 222, 52, 202, 251, 244, 17, 29, 154, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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