Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4674c9e5fc0096f6ba149304d643cb258ef5cd7458d6517dcbc75e8933e6c4f

Tx prefix hash: 66c851492a6962b24ab790006a26862ad2a80e249000d778a31c90bebe6dc8c3
Tx public key: dd0460f7a4da43d4a008a59fa265d78a2db9b094e8a438043f13bb5e24fd5d42
Timestamp: 1772689485 Timestamp [UTC]: 2026-03-05 05:44:45 Age [y:d:h:m:s]: 00:255:02:55:04
Block: 1491020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187755 RingCT/type: yes/0
Extra: 01dd0460f7a4da43d4a008a59fa265d78a2db9b094e8a438043f13bb5e24fd5d42021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 991ceefa5fd2cd631ce233fdad7f801cccccbe01a257cf2daf399e0896794913 0.000600000000 1980534 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": 1491030, "vin": [ { "gen": { "height": 1491020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "991ceefa5fd2cd631ce233fdad7f801cccccbe01a257cf2daf399e0896794913" } } ], "extra": [ 1, 221, 4, 96, 247, 164, 218, 67, 212, 160, 8, 165, 159, 162, 101, 215, 138, 45, 185, 176, 148, 232, 164, 56, 4, 63, 19, 187, 94, 36, 253, 93, 66, 2, 17, 0, 0, 0, 2, 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: