Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f91fac5a75c0b4722b2ca125b090f3561b62419ca7623517fe349158d0259944

Tx prefix hash: c961be8bd4bbf39b7aa13423c133b2e7045e1661b57431b0c61a6203ecb03b02
Tx public key: 8ede4e55f921dea5f67bcb609089bf6eebc74448e1524f8e9f283d7c5d8d2917
Timestamp: 1702498885 Timestamp [UCT]: 2023-12-13 20:21:25 Age [y:d:h:m:s]: 01:354:05:36:15
Block: 912461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512059 RingCT/type: yes/0
Extra: 018ede4e55f921dea5f67bcb609089bf6eebc74448e1524f8e9f283d7c5d8d291702110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05eebace965445a860a8bc2f04499172d637993d2b011d6e69f1da80d8fc5d7f 0.600000000000 1369689 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": 912471, "vin": [ { "gen": { "height": 912461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05eebace965445a860a8bc2f04499172d637993d2b011d6e69f1da80d8fc5d7f" } } ], "extra": [ 1, 142, 222, 78, 85, 249, 33, 222, 165, 246, 123, 203, 96, 144, 137, 191, 110, 235, 199, 68, 72, 225, 82, 79, 142, 159, 40, 61, 124, 93, 141, 41, 23, 2, 17, 0, 0, 0, 4, 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