Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5394651a7119cfe42d357d43f58f82b3c235a7a3d88ed8f2f4c70042b426f7e

Tx prefix hash: 4e384e3e60bd7361c3c4c7752d22446a7d011fe4950b75b1530ec54014a0d63c
Tx public key: a1fa36978044414e2612b810b9e5a2950777b0e3bf4bdf53bf2b990fb83903e6
Timestamp: 1572904634 Timestamp [UTC]: 2019-11-04 21:57:14 Age [y:d:h:m:s]: 06:320:22:09:32
Block: 828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0801 kB
Tx version: 2 No of confirmations: 1638303 RingCT/type: yes/0
Extra: 01a1fa36978044414e2612b810b9e5a2950777b0e3bf4bdf53bf2b990fb83903e6

1 output(s) for total of 0.609898264009 xmr

stealth address amount amount idx tag
00: fa6ac39e57dede76f4c98add8812ea028b1980704d54e9a70e76d3126be81df3 0.609898264009 784 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": 838, "vin": [ { "gen": { "height": 828 } } ], "vout": [ { "amount": 609898264009, "target": { "key": "fa6ac39e57dede76f4c98add8812ea028b1980704d54e9a70e76d3126be81df3" } } ], "extra": [ 1, 161, 250, 54, 151, 128, 68, 65, 78, 38, 18, 184, 16, 185, 229, 162, 149, 7, 119, 176, 227, 191, 75, 223, 83, 191, 43, 153, 15, 184, 57, 3, 230 ], "rct_signatures": { "type": 0 } }


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