Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e27e8265081f67e4fa0c4586e6d3a2b851ee99bb5b3d62ccb7fe467c237af3a4

Tx prefix hash: 2ae4bbe41439c8ba401cbc77d12eef2d2799f3df16ff0480f79acc0228db4c0c
Tx public key: 058716e2bf5d0e31d40c8775ab93cd6a18007468ac990ba3e095d60aa0f28350
Timestamp: 1711979037 Timestamp [UCT]: 2024-04-01 13:43:57 Age [y:d:h:m:s]: 01:034:19:50:37
Block: 991028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285894 RingCT/type: yes/0
Extra: 01058716e2bf5d0e31d40c8775ab93cd6a18007468ac990ba3e095d60aa0f283500211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e4ea01a8a4f944fbc37cd6d54daeb793a370b73cedffb62429d30c209ca5cae 0.600000000000 1451360 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 dinasty-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": 991038, "vin": [ { "gen": { "height": 991028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e4ea01a8a4f944fbc37cd6d54daeb793a370b73cedffb62429d30c209ca5cae" } } ], "extra": [ 1, 5, 135, 22, 226, 191, 93, 14, 49, 212, 12, 135, 117, 171, 147, 205, 106, 24, 0, 116, 104, 172, 153, 11, 163, 224, 149, 214, 10, 160, 242, 131, 80, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8