Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5340a71bb15de7f7dd088630a2a71a0763c3e3cad5b5af220f5cdc72fbf6fb91

Tx prefix hash: bd6253a47508b003a78f5d5567a788d560e50c1561f3d6222cdbf834470a1f76
Tx public key: 7569e53ea3c156c83d4e3f503b5d976d0dec6fef70cbf273918f8906a21ada21
Timestamp: 1773429625 Timestamp [UTC]: 2026-03-13 19:20:25 Age [y:d:h:m:s]: 00:249:19:00:26
Block: 1497142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184043 RingCT/type: yes/0
Extra: 017569e53ea3c156c83d4e3f503b5d976d0dec6fef70cbf273918f8906a21ada21021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 651011b43fd32e8e69b15efbfb1bff1f99bde30cab4da834d2d771b4d8d5ad30 0.000600000000 1986774 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": 1497152, "vin": [ { "gen": { "height": 1497142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "651011b43fd32e8e69b15efbfb1bff1f99bde30cab4da834d2d771b4d8d5ad30" } } ], "extra": [ 1, 117, 105, 229, 62, 163, 193, 86, 200, 61, 78, 63, 80, 59, 93, 151, 109, 13, 236, 111, 239, 112, 203, 242, 115, 145, 143, 137, 6, 162, 26, 218, 33, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: