Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d25b6b20f2ca9e5e5d6e6e30235100eacf7669b06fc36dd0b2a5d715b851ac3

Tx prefix hash: 583cfdb8675e2f9ea762ba3d2a5e2e8e71aadba97622b4e0c206c26df849d7ad
Tx public key: d643d7aed5fcdf6ba46b252034496cb170ca58e83a8370d61e2be672e937d8a2
Timestamp: 1579538241 Timestamp [UTC]: 2020-01-20 16:37:21 Age [y:d:h:m:s]: 06:303:23:45:27
Block: 49554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1631685 RingCT/type: yes/0
Extra: 01d643d7aed5fcdf6ba46b252034496cb170ca58e83a8370d61e2be672e937d8a202110000000c4ac5aa02000000000000000000

1 output(s) for total of 0.420540532992 xmr

stealth address amount amount idx tag
00: 8575fb59871efc34d47b770bfa8142f35831b5093819162e367894571f11362f 0.420540532992 92054 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": 49564, "vin": [ { "gen": { "height": 49554 } } ], "vout": [ { "amount": 420540532992, "target": { "key": "8575fb59871efc34d47b770bfa8142f35831b5093819162e367894571f11362f" } } ], "extra": [ 1, 214, 67, 215, 174, 213, 252, 223, 107, 164, 107, 37, 32, 52, 73, 108, 177, 112, 202, 88, 232, 58, 131, 112, 214, 30, 43, 230, 114, 233, 55, 216, 162, 2, 17, 0, 0, 0, 12, 74, 197, 170, 2, 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: