Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 308cf4c048083faebd2c8a63df151974704175631fbe8bf456a8ba10b74c6ff9

Tx prefix hash: 39fe613fb163cc224bd764918bfdfb2430bee15e94e5aff11e5d2942534690aa
Tx public key: 1058031efd3499490abd419284a485959ccd61eaa13140c14c0d3cb9773a4ead
Timestamp: 1765262602 Timestamp [UTC]: 2025-12-09 06:43:22 Age [y:d:h:m:s]: 00:342:13:52:01
Block: 1429665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250221 RingCT/type: yes/0
Extra: 011058031efd3499490abd419284a485959ccd61eaa13140c14c0d3cb9773a4ead02110000000770609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b269549ee91c36f0b5e5be49e4d87a1688dafef679cd2750655b1fb74c96e713 0.000600000000 1918396 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": 1429675, "vin": [ { "gen": { "height": 1429665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b269549ee91c36f0b5e5be49e4d87a1688dafef679cd2750655b1fb74c96e713" } } ], "extra": [ 1, 16, 88, 3, 30, 253, 52, 153, 73, 10, 189, 65, 146, 132, 164, 133, 149, 156, 205, 97, 234, 161, 49, 64, 193, 76, 13, 60, 185, 119, 58, 78, 173, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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: