Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13856b3fcf37273ad27e804f01c632412ac63c8e81d2f4778a113c8fb3aa87ab

Tx prefix hash: 45e587e69aab52ea295130e0becec3674b51212b2a997a9db58d17c3faeea82e
Tx public key: 6be66197ecb1b80ae500c19de514eb3ea04e361437777f304cf1d131a10831e1
Timestamp: 1772797409 Timestamp [UTC]: 2026-03-06 11:43:29 Age [y:d:h:m:s]: 00:260:14:49:55
Block: 1491906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191588 RingCT/type: yes/0
Extra: 016be66197ecb1b80ae500c19de514eb3ea04e361437777f304cf1d131a10831e1021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b8f82cfc804d10feeced2542cfb5aaf17ad4824f75ec5b88b5d9cb42f92cb1c7 0.000600000000 1981442 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": 1491916, "vin": [ { "gen": { "height": 1491906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8f82cfc804d10feeced2542cfb5aaf17ad4824f75ec5b88b5d9cb42f92cb1c7" } } ], "extra": [ 1, 107, 230, 97, 151, 236, 177, 184, 10, 229, 0, 193, 157, 229, 20, 235, 62, 160, 78, 54, 20, 55, 119, 127, 48, 76, 241, 209, 49, 161, 8, 49, 225, 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: