Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a486e44202eae4971ed53a49e7351c03c4aeb36a17a62245bf975185e53c189f

Tx prefix hash: 9c2a731a69461f43bc5c106af4e7c10bbbd3dbe5bb68a4b5c59d47499c9a36f2
Tx public key: 15a30ff1f1d6feeaef259358424761877eba66e89482d5e9d9a2526f25487a80
Timestamp: 1716211170 Timestamp [UCT]: 2024-05-20 13:19:30 Age [y:d:h:m:s]: 00:282:01:40:45
Block: 1026147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201581 RingCT/type: yes/0
Extra: 0115a30ff1f1d6feeaef259358424761877eba66e89482d5e9d9a2526f25487a8002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57deec09d40c3611dd73a683f01346caa3b6b04b73b13f84a617f2479f16d592 0.600000000000 1493072 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": 1026157, "vin": [ { "gen": { "height": 1026147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57deec09d40c3611dd73a683f01346caa3b6b04b73b13f84a617f2479f16d592" } } ], "extra": [ 1, 21, 163, 15, 241, 241, 214, 254, 234, 239, 37, 147, 88, 66, 71, 97, 135, 126, 186, 102, 232, 148, 130, 213, 233, 217, 162, 82, 111, 37, 72, 122, 128, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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