Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66c6be44dcea8fb5310078e4e9446227523d46cb55523ba48dd11e380deae3d1

Tx prefix hash: d38f7d8d23b29feb31c7459d56785ed8223f644fbcf966fce0ca0a339ad3db32
Tx public key: 1026811b93046f856ddb7ab33a6b0cf5dba33deb9ddfc2d92c2e974ae877f0b0
Timestamp: 1743632717 Timestamp [UTC]: 2025-04-02 22:25:17 Age [y:d:h:m:s]: 01:233:20:28:16
Block: 1252980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430514 RingCT/type: yes/0
Extra: 011026811b93046f856ddb7ab33a6b0cf5dba33deb9ddfc2d92c2e974ae877f0b0021100000001a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9ead9319340881e734504275b8edbfedfd46285c09da9662b21172267e362c84 0.000600000000 1740061 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": 1252990, "vin": [ { "gen": { "height": 1252980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ead9319340881e734504275b8edbfedfd46285c09da9662b21172267e362c84" } } ], "extra": [ 1, 16, 38, 129, 27, 147, 4, 111, 133, 109, 219, 122, 179, 58, 107, 12, 245, 219, 163, 61, 235, 157, 223, 194, 217, 44, 46, 151, 74, 232, 119, 240, 176, 2, 17, 0, 0, 0, 1, 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: