Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 332a2d0c2d83ac7dc95a34a7dad3d1bba29ba43eccb9d277d7c2babc1fb724a0

Tx prefix hash: d2a6ad803790d641e88d857b1f3dbece4757ba300d25369d165602fbf68ebea2
Tx public key: 6bd1aab9ce8cdd787650c6abfdb310930e7c602df957512f7e26e7bd415dd539
Timestamp: 1744702528 Timestamp [UTC]: 2025-04-15 07:35:28 Age [y:d:h:m:s]: 01:213:06:34:15
Block: 1261841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416344 RingCT/type: yes/0
Extra: 016bd1aab9ce8cdd787650c6abfdb310930e7c602df957512f7e26e7bd415dd5390211000000056c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8cb5bc9f3224948d3fc8937e03cdecd53dc5d5dc1be08b405e8de4cbcda5700b 0.000600000000 1749016 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": 1261851, "vin": [ { "gen": { "height": 1261841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cb5bc9f3224948d3fc8937e03cdecd53dc5d5dc1be08b405e8de4cbcda5700b" } } ], "extra": [ 1, 107, 209, 170, 185, 206, 140, 221, 120, 118, 80, 198, 171, 253, 179, 16, 147, 14, 124, 96, 45, 249, 87, 81, 47, 126, 38, 231, 189, 65, 93, 213, 57, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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: