Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 468fb2babbe9e865e035016cc6de5f354f015e43a319b2cef2411758ef07ccc1

Tx prefix hash: 1c15cdb3b710894803d78cd5d80b75c67dbb604f80211b48d5871a23204d83e1
Tx public key: 35ec3cb2e5ed62c17514036c3503d079e853e3141a9017fc1480c24b4e418304
Timestamp: 1696156145 Timestamp [UCT]: 2023-10-01 10:29:05 Age [y:d:h:m:s]: 01:192:12:39:19
Block: 860084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398647 RingCT/type: yes/0
Extra: 0135ec3cb2e5ed62c17514036c3503d079e853e3141a9017fc1480c24b4e4183040211000000014b8f5122000000000000000000

1 output(s) for total of 0.867330686000 dcy

stealth address amount amount idx
00: 4cad2ebe75394cb8483cb9377e5bf1540fbac5c6fbab383574426957c2190ac6 0.867330686000 1314346 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": 860094, "vin": [ { "gen": { "height": 860084 } } ], "vout": [ { "amount": 867330686, "target": { "key": "4cad2ebe75394cb8483cb9377e5bf1540fbac5c6fbab383574426957c2190ac6" } } ], "extra": [ 1, 53, 236, 60, 178, 229, 237, 98, 193, 117, 20, 3, 108, 53, 3, 208, 121, 232, 83, 227, 20, 26, 144, 23, 252, 20, 128, 194, 75, 78, 65, 131, 4, 2, 17, 0, 0, 0, 1, 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