Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78fd2107b21346a3a606d8a2a3be1bbb8fb2c0c5e433aa2e59815514d0c3023f

Tx prefix hash: 1e04d72d8e462e2ed0a3fd4f3c6bf2820ea0c523dea7b30dc58a013ffc40bcf0
Tx public key: 0a1ef078ae0183f06030977158d2631e10770736c0a40ac6012df89911b6f82e
Timestamp: 1753552421 Timestamp [UTC]: 2025-07-26 17:53:41 Age [y:d:h:m:s]: 00:298:10:00:09
Block: 1333943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205508 RingCT/type: yes/0
Extra: 010a1ef078ae0183f06030977158d2631e10770736c0a40ac6012df89911b6f82e021100000001a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 257191337179de6bb1cd175162457ea70a867e7ced7e47f748c0fcc04ea09971 0.000600000000 1821742 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": 1333953, "vin": [ { "gen": { "height": 1333943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "257191337179de6bb1cd175162457ea70a867e7ced7e47f748c0fcc04ea09971" } } ], "extra": [ 1, 10, 30, 240, 120, 174, 1, 131, 240, 96, 48, 151, 113, 88, 210, 99, 30, 16, 119, 7, 54, 192, 164, 10, 198, 1, 45, 248, 153, 17, 182, 248, 46, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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: