Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d261f8088d60743a2dc4d041306b6fa6ca9794ea910b4fa0ffdb215043b12a45

Tx prefix hash: 366e8ae3f9fad7d2de5f9ff6dca5eb42ac79a6c8ebf5b4e17dcce1380e11fa20
Tx public key: 0944d3636959f642bc5d9063d3be832c594c98b2bd02073d16aee67a605898ee
Timestamp: 1743516230 Timestamp [UTC]: 2025-04-01 14:03:50 Age [y:d:h:m:s]: 01:234:11:40:49
Block: 1252017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431477 RingCT/type: yes/0
Extra: 010944d3636959f642bc5d9063d3be832c594c98b2bd02073d16aee67a605898ee021100000002a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 03ddd6621a274a9fd60003500afc63e396127c1e1dac36d754833d410095d3f2 0.000600000000 1739094 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": 1252027, "vin": [ { "gen": { "height": 1252017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03ddd6621a274a9fd60003500afc63e396127c1e1dac36d754833d410095d3f2" } } ], "extra": [ 1, 9, 68, 211, 99, 105, 89, 246, 66, 188, 93, 144, 99, 211, 190, 131, 44, 89, 76, 152, 178, 189, 2, 7, 61, 22, 174, 230, 122, 96, 88, 152, 238, 2, 17, 0, 0, 0, 2, 162, 237, 1, 107, 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: