Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f73d7271fc52374ff342a04993b6984f576246e6a01c085ecca35f5b928b49f

Tx prefix hash: 5fe594d99883ca50abaa0c36f39cb1f1e21111c5f73011af3ce1f1d937efa21f
Tx public key: dd403a05564224f44142d562552e652e623a967cf548dc85f42dd1a87e99eaca
Timestamp: 1707308012 Timestamp [UTC]: 2024-02-07 12:13:32 Age [y:d:h:m:s]: 02:101:15:11:13
Block: 952323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 585333 RingCT/type: yes/0
Extra: 01dd403a05564224f44142d562552e652e623a967cf548dc85f42dd1a87e99eaca02110000000652d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1cf4499ebee9a7de7e59467d9f1c1293c892c86a6acf1ac607a32419ab27a993 0.000600000000 1411245 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": 952333, "vin": [ { "gen": { "height": 952323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cf4499ebee9a7de7e59467d9f1c1293c892c86a6acf1ac607a32419ab27a993" } } ], "extra": [ 1, 221, 64, 58, 5, 86, 66, 36, 244, 65, 66, 213, 98, 85, 46, 101, 46, 98, 58, 150, 124, 245, 72, 220, 133, 244, 45, 209, 168, 126, 153, 234, 202, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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: