Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 060a78ccf124b06c1dcfac3fbb8186aebe1af590ff48587fa25a46c21d2db784

Tx prefix hash: d5e5904cfbd8d4442b5cd9698dadcd536d3306a99802f16b7dcb5898b3a5391a
Tx public key: f40b2167b04e821eba7f798f32d8f2df86e8b9a0d1a821ce4b8f18e908f5b443
Timestamp: 1770844064 Timestamp [UTC]: 2026-02-11 21:07:44 Age [y:d:h:m:s]: 00:000:11:05:49
Block: 1475757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 337 RingCT/type: yes/0
Extra: 01f40b2167b04e821eba7f798f32d8f2df86e8b9a0d1a821ce4b8f18e908f5b44302087dad067b2d25ef21

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f5c4a128c6b446e62a40d2d80c2f0553228234ce00821e14d9d44ca1e8e4c260 0.000600000000 1965061 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": 1475767, "vin": [ { "gen": { "height": 1475757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5c4a128c6b446e62a40d2d80c2f0553228234ce00821e14d9d44ca1e8e4c260" } } ], "extra": [ 1, 244, 11, 33, 103, 176, 78, 130, 30, 186, 127, 121, 143, 50, 216, 242, 223, 134, 232, 185, 160, 209, 168, 33, 206, 75, 143, 24, 233, 8, 245, 180, 67, 2, 8, 125, 173, 6, 123, 45, 37, 239, 33 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369