Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df2f82a6dcc7e156ba500ca392408841279fdd399ddc7caf54f10bb4f445c82e

Tx prefix hash: e9cc4800b31675812867e060ae9739fdbfd528575f53eecbbf53ca971512fe92
Tx public key: 7acc44996cf3c1c09e34d857404180c39edd760d40cb6efb43af62b1ec71d90d
Timestamp: 1742297587 Timestamp [UTC]: 2025-03-18 11:33:07 Age [y:d:h:m:s]: 01:248:03:08:15
Block: 1241960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441516 RingCT/type: yes/0
Extra: 017acc44996cf3c1c09e34d857404180c39edd760d40cb6efb43af62b1ec71d90d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a610f9293e84182d951366b65a5ee7e8343d65d3b7fd66da13aa54a981bd5aea 0.000600000000 1728933 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": 1241970, "vin": [ { "gen": { "height": 1241960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a610f9293e84182d951366b65a5ee7e8343d65d3b7fd66da13aa54a981bd5aea" } } ], "extra": [ 1, 122, 204, 68, 153, 108, 243, 193, 192, 158, 52, 216, 87, 64, 65, 128, 195, 158, 221, 118, 13, 64, 203, 110, 251, 67, 175, 98, 177, 236, 113, 217, 13, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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: