Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5765bacf02837f05f9681a9b809ea285b601e7a32eff9c0640d4bd9c8129d22

Tx prefix hash: bfde8180d6ce515b03677755a7614bb38ff1eaa981902598c99ebcef8b6afd86
Tx public key: 0d68b194b5a017e8fe9095bd04b73fe599592e2f36325cec047fcbd64a75e468
Timestamp: 1620384455 Timestamp [UCT]: 2021-05-07 10:47:35 Age [y:d:h:m:s]: 04:177:20:06:49
Block: 255929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145835 RingCT/type: yes/0
Extra: 010d68b194b5a017e8fe9095bd04b73fe599592e2f36325cec047fcbd64a75e46802110000005b0dc70aa7000000000000000000

1 output(s) for total of 87.096666448000 dcy

stealth address amount amount idx
00: fd9649ca294dfc9d7fff5f5249be9cc40f13d02733cc86b520081688a0557420 87.096666448000 538282 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": 255939, "vin": [ { "gen": { "height": 255929 } } ], "vout": [ { "amount": 87096666448, "target": { "key": "fd9649ca294dfc9d7fff5f5249be9cc40f13d02733cc86b520081688a0557420" } } ], "extra": [ 1, 13, 104, 177, 148, 181, 160, 23, 232, 254, 144, 149, 189, 4, 183, 63, 229, 153, 89, 46, 47, 54, 50, 92, 236, 4, 127, 203, 214, 74, 117, 228, 104, 2, 17, 0, 0, 0, 91, 13, 199, 10, 167, 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