Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e06baed6a2c4819d6c337a7d18a10dd34cf8b80b6945a8924a1c8a565044fa05

Tx prefix hash: 09384d3f77a42dbf2edf0ca6c36e4e090a1d3276f33acfe921228a3b6c9beb8f
Tx public key: 3ca4dd2c82c40df4c1751d0648031c1a95bb5ba6aff50eca2bc5d7b0f17e203d
Timestamp: 1741393122 Timestamp [UTC]: 2025-03-08 00:18:42 Age [y:d:h:m:s]: 01:254:13:42:56
Block: 1234455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445969 RingCT/type: yes/0
Extra: 013ca4dd2c82c40df4c1751d0648031c1a95bb5ba6aff50eca2bc5d7b0f17e203d0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dc853d172c8269d18d787b7db608ae494349853d54c7245cb54ecdc9db969dd4 0.000600000000 1721382 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": 1234465, "vin": [ { "gen": { "height": 1234455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc853d172c8269d18d787b7db608ae494349853d54c7245cb54ecdc9db969dd4" } } ], "extra": [ 1, 60, 164, 221, 44, 130, 196, 13, 244, 193, 117, 29, 6, 72, 3, 28, 26, 149, 187, 91, 166, 175, 245, 14, 202, 43, 197, 215, 176, 241, 126, 32, 61, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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: