Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29f0fed755055baa73bb45a1dd950c969a7b7be0ca5a8431bb98339e649c9ff1

Tx prefix hash: ed958590d4e53fab831a23e467806dcd713cab1582225876c3fd6f4b9393cf06
Tx public key: bb4391448eb0f146354392128c21225f4e8ce3ce3228a87cf6c0d612491c8793
Timestamp: 1774713170 Timestamp [UTC]: 2026-03-28 15:52:50 Age [y:d:h:m:s]: 00:239:06:24:43
Block: 1507758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176392 RingCT/type: yes/0
Extra: 01bb4391448eb0f146354392128c21225f4e8ce3ce3228a87cf6c0d612491c8793021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3f5e82db0591cf1601ae841b35022d96b0f57d4043053576f76c42bae4c2cb2e 0.000600000000 1997510 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": 1507768, "vin": [ { "gen": { "height": 1507758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f5e82db0591cf1601ae841b35022d96b0f57d4043053576f76c42bae4c2cb2e" } } ], "extra": [ 1, 187, 67, 145, 68, 142, 176, 241, 70, 53, 67, 146, 18, 140, 33, 34, 95, 78, 140, 227, 206, 50, 40, 168, 124, 246, 192, 214, 18, 73, 28, 135, 147, 2, 17, 0, 0, 0, 6, 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: