Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 819425677d21bf17e1abbf644080487e1f4e4c43e4d84256171ff70d1e25e623

Tx prefix hash: 106300833ff619ce892fb9c96ffeb48f2589289938edcc586e53022e25301c19
Tx public key: ca5bf2e45552fdd63d3fb85e733effe60a36da3bf68e919bc95fc1d5f3126833
Timestamp: 1771355429 Timestamp [UTC]: 2026-02-17 19:10:29 Age [y:d:h:m:s]: 00:273:01:52:20
Block: 1479957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200681 RingCT/type: yes/0
Extra: 01ca5bf2e45552fdd63d3fb85e733effe60a36da3bf68e919bc95fc1d5f3126833021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6cfa9eac8f8b791faaa364e716d4c6a9293b8e838ca42370c3204f78939372d 0.000600000000 1969317 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": 1479967, "vin": [ { "gen": { "height": 1479957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6cfa9eac8f8b791faaa364e716d4c6a9293b8e838ca42370c3204f78939372d" } } ], "extra": [ 1, 202, 91, 242, 228, 85, 82, 253, 214, 61, 63, 184, 94, 115, 62, 255, 230, 10, 54, 218, 59, 246, 142, 145, 155, 201, 95, 193, 213, 243, 18, 104, 51, 2, 17, 0, 0, 0, 1, 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: