Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca63d2a813bb17ba3fcc9e336a988f6650568fea5c03e1ddd584fc95667896e8

Tx prefix hash: 5e85d073f1b3c512e7fa9bc2270424eca785fa15cbe2f3f4c176060c1b6866a3
Tx public key: b5ec3f835fdb52a6a2be468217f46c108ee3b6c629ef0bb6fe59a1c0d53617de
Timestamp: 1638687283 Timestamp [UTC]: 2021-12-05 06:54:43 Age [y:d:h:m:s]: 04:158:12:45:53
Block: 388785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1142753 RingCT/type: yes/0
Extra: 01b5ec3f835fdb52a6a2be468217f46c108ee3b6c629ef0bb6fe59a1c0d53617de021100000002b494d89c000000000000000000

1 output(s) for total of 0.031607800136 xmr

stealth address amount amount idx tag
00: a3dc40959c6261a620eac49fd8e3b717c45ebb2104ecfb472c55834392e41e9b 0.031607800136 783634 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 dinastycoin-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": 388795, "vin": [ { "gen": { "height": 388785 } } ], "vout": [ { "amount": 31607800136, "target": { "key": "a3dc40959c6261a620eac49fd8e3b717c45ebb2104ecfb472c55834392e41e9b" } } ], "extra": [ 1, 181, 236, 63, 131, 95, 219, 82, 166, 162, 190, 70, 130, 23, 244, 108, 16, 142, 227, 182, 198, 41, 239, 11, 182, 254, 89, 161, 192, 213, 54, 23, 222, 2, 17, 0, 0, 0, 2, 180, 148, 216, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: