Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0fbb7b6fc63c777e5bbd94b62ce1f49d8d4fcf4ebec24ed15dcddcc0e86131

Tx prefix hash: 69ef81eba7b26d72e07bbf080bb28113734636393112a338c45fa822b63476e4
Tx public key: 8744e064360759d680967a852d41e25cdea2eb1e053317e7fbd418a8fe27e535
Timestamp: 1773128135 Timestamp [UTC]: 2026-03-10 07:35:35 Age [y:d:h:m:s]: 00:253:06:27:40
Block: 1494635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186538 RingCT/type: yes/0
Extra: 018744e064360759d680967a852d41e25cdea2eb1e053317e7fbd418a8fe27e535021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4e53482417a8978580d587d6f29199641df70906fb44794c95e5e6b4ed3b7db5 0.000600000000 1984207 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": 1494645, "vin": [ { "gen": { "height": 1494635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e53482417a8978580d587d6f29199641df70906fb44794c95e5e6b4ed3b7db5" } } ], "extra": [ 1, 135, 68, 224, 100, 54, 7, 89, 214, 128, 150, 122, 133, 45, 65, 226, 92, 222, 162, 235, 30, 5, 51, 23, 231, 251, 212, 24, 168, 254, 39, 229, 53, 2, 17, 0, 0, 0, 2, 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: