Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d06ceea4e34865464c49d319d53258eca540d4a106f5a2f513ba21a10f914e6

Tx prefix hash: 2011d7ceafe13c96da4460e51d902d44deb96345115b1de79eb74710900bc1cd
Tx public key: 38e787d53cb2acc42a1f3cb871a6feb02b64c8d8772cde21890775cd884af7be
Timestamp: 1756707026 Timestamp [UTC]: 2025-09-01 06:10:26 Age [y:d:h:m:s]: 01:080:17:59:42
Block: 1358891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324136 RingCT/type: yes/0
Extra: 0138e787d53cb2acc42a1f3cb871a6feb02b64c8d8772cde21890775cd884af7be021100000006ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a452dd0db6503f69b029cfc3e0f5528b231b61909195e0e680e2cff444e68315 0.000600000000 1846904 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": 1358901, "vin": [ { "gen": { "height": 1358891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a452dd0db6503f69b029cfc3e0f5528b231b61909195e0e680e2cff444e68315" } } ], "extra": [ 1, 56, 231, 135, 213, 60, 178, 172, 196, 42, 31, 60, 184, 113, 166, 254, 176, 43, 100, 200, 216, 119, 44, 222, 33, 137, 7, 117, 205, 136, 74, 247, 190, 2, 17, 0, 0, 0, 6, 173, 121, 72, 208, 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: