Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90cf6bf3714ef58ed2ae46aa24e21c5d6c8bb7e40d66a8ca3e2eeb31bc994774

Tx prefix hash: 0ace96f699b75e0f47d704154e1ea80f6974cf54dee5faf60988b759f8e6b00d
Tx public key: 21580f4d84895cca9f21f7edd81e039fd4c546f6fc27c9bbbc2e1dfecc3188ce
Timestamp: 1774349906 Timestamp [UTC]: 2026-03-24 10:58:26 Age [y:d:h:m:s]: 00:237:12:14:49
Block: 1504737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175251 RingCT/type: yes/0
Extra: 0121580f4d84895cca9f21f7edd81e039fd4c546f6fc27c9bbbc2e1dfecc3188ce021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: da2ca501e245abea1ec9e311bb221fcad3918209810710cb1fd865e9fffb1426 0.000600000000 1994463 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": 1504747, "vin": [ { "gen": { "height": 1504737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da2ca501e245abea1ec9e311bb221fcad3918209810710cb1fd865e9fffb1426" } } ], "extra": [ 1, 33, 88, 15, 77, 132, 137, 92, 202, 159, 33, 247, 237, 216, 30, 3, 159, 212, 197, 70, 246, 252, 39, 201, 187, 188, 46, 29, 254, 204, 49, 136, 206, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: