Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0a6ecfe874ec7acfe80e3a48720876077840b92fec5bdfb0ff78f0d250e90d3

Tx prefix hash: dd47332b1d1a00789f7bf63660f60806f769aa12149fb2370a13fc9a84a376e1
Tx public key: a4dfa2dc9f1917463ada7b3de623cdbd5a05e76e34e17256ed0f09a1e8a03197
Timestamp: 1710374638 Timestamp [UCT]: 2024-03-14 00:03:58 Age [y:d:h:m:s]: 01:049:23:49:19
Block: 977773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296722 RingCT/type: yes/0
Extra: 01a4dfa2dc9f1917463ada7b3de623cdbd5a05e76e34e17256ed0f09a1e8a031970211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa7125b325b40ebc1e4d5574b99506af19415a6fb7608956ec73f69eaba11e51 0.600000000000 1437780 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": 977783, "vin": [ { "gen": { "height": 977773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa7125b325b40ebc1e4d5574b99506af19415a6fb7608956ec73f69eaba11e51" } } ], "extra": [ 1, 164, 223, 162, 220, 159, 25, 23, 70, 58, 218, 123, 61, 230, 35, 205, 189, 90, 5, 231, 110, 52, 225, 114, 86, 237, 15, 9, 161, 232, 160, 49, 151, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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