Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a17bb02e3d63cbcefcaee342fbcfc521d26f264bb79ac86da89a31732a909888

Tx prefix hash: 6b9cf3f284e7ab78147c7c770f8252536f4a09e3e1d821b758d7beb5b6528a6b
Tx public key: 5d799ed79ae0adc399f52a509bb4ddd504ede5b8b8f354f7b02bd0e27d5b16cc
Timestamp: 1773978919 Timestamp [UTC]: 2026-03-20 03:55:19 Age [y:d:h:m:s]: 00:240:03:28:04
Block: 1501651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177077 RingCT/type: yes/0
Extra: 015d799ed79ae0adc399f52a509bb4ddd504ede5b8b8f354f7b02bd0e27d5b16cc021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b84855591e15635188c746c7a928410c5c2e44fa46f09c2b45c3dd803bed563c 0.000600000000 1991337 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 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": 1501661, "vin": [ { "gen": { "height": 1501651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b84855591e15635188c746c7a928410c5c2e44fa46f09c2b45c3dd803bed563c" } } ], "extra": [ 1, 93, 121, 158, 215, 154, 224, 173, 195, 153, 245, 42, 80, 155, 180, 221, 213, 4, 237, 229, 184, 184, 243, 84, 247, 176, 43, 208, 226, 125, 91, 22, 204, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: