Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d0202fa9facbaefb0eb14d01d9e5dae47f6d089327492c839e5d42f9479ccee

Tx prefix hash: 6804becde9194272b473a51a89f7fd3df871081ee9dd7c480f37921f3b4423aa
Tx public key: 694cba80e82d973520ffef3d69f89112b27a8468700f304db32c26daf4f4873a
Timestamp: 1747771192 Timestamp [UTC]: 2025-05-20 19:59:52 Age [y:d:h:m:s]: 01:183:08:11:39
Block: 1287264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395124 RingCT/type: yes/0
Extra: 01694cba80e82d973520ffef3d69f89112b27a8468700f304db32c26daf4f4873a0211000000041f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 99cccbef989750a7a519d9082f63a43b61ac5f1c6cd8440329076a66e987fc64 0.000600000000 1774731 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": 1287274, "vin": [ { "gen": { "height": 1287264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99cccbef989750a7a519d9082f63a43b61ac5f1c6cd8440329076a66e987fc64" } } ], "extra": [ 1, 105, 76, 186, 128, 232, 45, 151, 53, 32, 255, 239, 61, 105, 248, 145, 18, 178, 122, 132, 104, 112, 15, 48, 77, 179, 44, 38, 218, 244, 244, 135, 58, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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: