Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d40da1c11c08d97a2a67869913a573eadde013a384dad62310a0d7a86f9fe7b3

Tx prefix hash: f9261437770c02f6be19b980d97e56a93a1bb7ad52d3200943bb2798964ff5f4
Tx public key: 334a739766092999ce152b0b4e916ec9c740cdd2ebeb1b471481ee87d2b6d25e
Timestamp: 1772571583 Timestamp [UTC]: 2026-03-03 20:59:43 Age [y:d:h:m:s]: 00:260:15:18:08
Block: 1490032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191847 RingCT/type: yes/0
Extra: 01334a739766092999ce152b0b4e916ec9c740cdd2ebeb1b471481ee87d2b6d25e021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4e8bba833afa46a1bc7020e5a86db39dc76cdc5ca07ea2f1c752499986b06bbf 0.000600000000 1979532 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": 1490042, "vin": [ { "gen": { "height": 1490032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e8bba833afa46a1bc7020e5a86db39dc76cdc5ca07ea2f1c752499986b06bbf" } } ], "extra": [ 1, 51, 74, 115, 151, 102, 9, 41, 153, 206, 21, 43, 11, 78, 145, 110, 201, 199, 64, 205, 210, 235, 235, 27, 71, 20, 129, 238, 135, 210, 182, 210, 94, 2, 17, 0, 0, 0, 4, 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: