Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1966e30b2c36073bb3e88536d5d8dedbce4a8953964994ef1020512f6991b01

Tx prefix hash: 21159668220d19e9656a3186fda3032208a1649ff3a2d90c81ade4c49c03e5fe
Tx public key: 7e98c02cf0b98caa0dee96493a115f1f46814d2ee98e77cf270a5c4602f1fe87
Timestamp: 1728811367 Timestamp [UTC]: 2024-10-13 09:22:47 Age [y:d:h:m:s]: 02:040:09:54:35
Block: 1130611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 553539 RingCT/type: yes/0
Extra: 017e98c02cf0b98caa0dee96493a115f1f46814d2ee98e77cf270a5c4602f1fe8702110000000991e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0e5a26f8f6c999afa80459ab89eaf683dce377e2ed4c95b03a275a8c95d35c1c 0.000600000000 1613488 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": 1130621, "vin": [ { "gen": { "height": 1130611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e5a26f8f6c999afa80459ab89eaf683dce377e2ed4c95b03a275a8c95d35c1c" } } ], "extra": [ 1, 126, 152, 192, 44, 240, 185, 140, 170, 13, 238, 150, 73, 58, 17, 95, 31, 70, 129, 77, 46, 233, 142, 119, 207, 39, 10, 92, 70, 2, 241, 254, 135, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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: