Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56b26a4815a6c8bfaad831218cd61e93efead05a6ca21af55bc46f6b57cd93a3

Tx prefix hash: e9633be3839b75565d238a953768f7c239fb1ea65bf422ea69fe249652227395
Tx public key: 3042607d0d3c100cdb01f0463e5a1f5056965e49e7d5c075358e642bf9176761
Timestamp: 1738140440 Timestamp [UTC]: 2025-01-29 08:47:20 Age [y:d:h:m:s]: 01:043:15:51:18
Block: 1207526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289761 RingCT/type: yes/0
Extra: 013042607d0d3c100cdb01f0463e5a1f5056965e49e7d5c075358e642bf91767610211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5b123cccbff19628a2ecc9dd99a62a2a825ee48ea4f9182712a9083ac4745c93 0.000600000000 1694249 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": 1207536, "vin": [ { "gen": { "height": 1207526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b123cccbff19628a2ecc9dd99a62a2a825ee48ea4f9182712a9083ac4745c93" } } ], "extra": [ 1, 48, 66, 96, 125, 13, 60, 16, 12, 219, 1, 240, 70, 62, 90, 31, 80, 86, 150, 94, 73, 231, 213, 192, 117, 53, 142, 100, 43, 249, 23, 103, 97, 2, 17, 0, 0, 0, 1, 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) | dinastycoin version: tesla-369