Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d174e2dfd3cbb4f0d1c57d0c63f1abdebb6c9dfa559b1290676e91e2e594e37e

Tx prefix hash: 2f64e81eb4a022a89871fbd85480daffdd0742249d0a66389d93ae1b15011b6e
Tx public key: 058f9be5d558a905c83ed24eb9f93685cb10908ed82a9673b898102e3a69b02c
Timestamp: 1767381436 Timestamp [UTC]: 2026-01-02 19:17:16 Age [y:d:h:m:s]: 00:321:22:02:35
Block: 1447233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 235619 RingCT/type: yes/0
Extra: 01058f9be5d558a905c83ed24eb9f93685cb10908ed82a9673b898102e3a69b02c020900000008f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ef661acfe55dec5e42a8c839dee00221734f463901be907f829bb854cd45cc0f 0.000600000000 1936191 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": 1447243, "vin": [ { "gen": { "height": 1447233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef661acfe55dec5e42a8c839dee00221734f463901be907f829bb854cd45cc0f" } } ], "extra": [ 1, 5, 143, 155, 229, 213, 88, 169, 5, 200, 62, 210, 78, 185, 249, 54, 133, 203, 16, 144, 142, 216, 42, 150, 115, 184, 152, 16, 46, 58, 105, 176, 44, 2, 9, 0, 0, 0, 8, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: