Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2a0f0ea4ab83446296b6a1042deaceb5fde9305e886538d8e4b9be807f6119e

Tx prefix hash: a0bbc40fe79d3e8184214ffeb11ed16019f75646b8bc1dfda21da3cc0b097e31
Tx public key: 16c489fa1f8e9c2d7551a29dff07bfdde539ed9d54e9b86b712083b6d7300774
Timestamp: 1576112952 Timestamp [UTC]: 2019-12-12 01:09:12 Age [y:d:h:m:s]: 06:153:09:50:04
Block: 25720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1506344 RingCT/type: yes/0
Extra: 0116c489fa1f8e9c2d7551a29dff07bfdde539ed9d54e9b86b712083b6d730077402110000006dad433a0b000000000000000000

1 output(s) for total of 0.504457301178 xmr

stealth address amount amount idx tag
00: 88ca89c57bd96e172d28c936fad9bc6061948d89cc9f619c79829ff0d4811ac5 0.504457301178 42473 of 0 -

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": 25730, "vin": [ { "gen": { "height": 25720 } } ], "vout": [ { "amount": 504457301178, "target": { "key": "88ca89c57bd96e172d28c936fad9bc6061948d89cc9f619c79829ff0d4811ac5" } } ], "extra": [ 1, 22, 196, 137, 250, 31, 142, 156, 45, 117, 81, 162, 157, 255, 7, 191, 221, 229, 57, 237, 157, 84, 233, 184, 107, 113, 32, 131, 182, 215, 48, 7, 116, 2, 17, 0, 0, 0, 109, 173, 67, 58, 11, 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: