Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c67927cc7e7d55dc6e065b9602bc113f9f3b1036748e75d8e133cd49ca345e32

Tx prefix hash: 29449132044f1e3c3b66fe8254e22477aec3e7e9440dfca9028d119775c73b9e
Tx public key: 6e1a735393cd131053421b6d5369e501bb4b105c1719826468f9f7e72d79375e
Timestamp: 1583632915 Timestamp [UTC]: 2020-03-08 02:01:55 Age [y:d:h:m:s]: 05:357:09:16:20
Block: 78311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1408561 RingCT/type: yes/0
Extra: 016e1a735393cd131053421b6d5369e501bb4b105c1719826468f9f7e72d79375e0211000000018e602c4c000000000000000000

1 output(s) for total of 0.337694463922 xmr

stealth address amount amount idx tag
00: ea848ed101c1f92ad33ff376105922f8c5cd5c34e1dc4fe2253047c06ccbedd0 0.337694463922 143755 of 0 -

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": 78321, "vin": [ { "gen": { "height": 78311 } } ], "vout": [ { "amount": 337694463922, "target": { "key": "ea848ed101c1f92ad33ff376105922f8c5cd5c34e1dc4fe2253047c06ccbedd0" } } ], "extra": [ 1, 110, 26, 115, 83, 147, 205, 19, 16, 83, 66, 27, 109, 83, 105, 229, 1, 187, 75, 16, 92, 23, 25, 130, 100, 104, 249, 247, 231, 45, 121, 55, 94, 2, 17, 0, 0, 0, 1, 142, 96, 44, 76, 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