Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7b58c2ba109f3d6643659997b752725cf29fa964edfa9919403c4ec5c2d8a55

Tx prefix hash: c1474fee11adec6408aaeeda1bd5b6d40a830cd17a80dfc3e32692417cdf1cdb
Tx public key: 6fff7ed10924cfdf0cdcfdff97ac8ee024e42781738a1fe11cdcd5ff5a589929
Timestamp: 1746219956 Timestamp [UTC]: 2025-05-02 21:05:56 Age [y:d:h:m:s]: 01:012:06:51:59
Block: 1274406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259683 RingCT/type: yes/0
Extra: 016fff7ed10924cfdf0cdcfdff97ac8ee024e42781738a1fe11cdcd5ff5a58992902110000000201491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 108005a73f236b3d34ef35b1d8cbc74e5c2b1bd72318702e8f4b653e15f33609 0.000600000000 1761701 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": 1274416, "vin": [ { "gen": { "height": 1274406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "108005a73f236b3d34ef35b1d8cbc74e5c2b1bd72318702e8f4b653e15f33609" } } ], "extra": [ 1, 111, 255, 126, 209, 9, 36, 207, 223, 12, 220, 253, 255, 151, 172, 142, 224, 36, 228, 39, 129, 115, 138, 31, 225, 28, 220, 213, 255, 90, 88, 153, 41, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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: