Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bd11b55447aad211b1a1a6be1774b2b6ca39e3529abb92c4a56f0ab916ec7f4

Tx prefix hash: 19217bf257fa02d63cd07cc3e9eed402acfbc02a8a4462d797a6773dcc2ab88e
Tx public key: 0ceb7f9e434b5dfca751a30dd9fec19f63dae145e973456ef2e2244c0d6becaa
Timestamp: 1698343049 Timestamp [UCT]: 2023-10-26 17:57:29 Age [y:d:h:m:s]: 01:142:18:12:48
Block: 878230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363034 RingCT/type: yes/0
Extra: 010ceb7f9e434b5dfca751a30dd9fec19f63dae145e973456ef2e2244c0d6becaa0211000000044b8f5122000000000000000000

1 output(s) for total of 0.755195606000 dcy

stealth address amount amount idx
00: 0528ad4d39734a957df85d52966c24e12519353007cceeac93bb9d02967d65e1 0.755195606000 1333656 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": 878240, "vin": [ { "gen": { "height": 878230 } } ], "vout": [ { "amount": 755195606, "target": { "key": "0528ad4d39734a957df85d52966c24e12519353007cceeac93bb9d02967d65e1" } } ], "extra": [ 1, 12, 235, 127, 158, 67, 75, 93, 252, 167, 81, 163, 13, 217, 254, 193, 159, 99, 218, 225, 69, 233, 115, 69, 110, 242, 226, 36, 76, 13, 107, 236, 170, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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