Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0c7e79edfd0f17826575254e0c7b17e68561edd8218b7616ad093285d3479a0

Tx prefix hash: faa53552aa240c3532085a0e2c84dc8f0ba1d894ec839e6b965a7822fb930c23
Tx public key: 03ce414d1040af399ec72852ffa943b0656bb5e10afd21f233b0589ea4f0e5af
Timestamp: 1731288291 Timestamp [UCT]: 2024-11-11 01:24:51 Age [y:d:h:m:s]: 00:158:10:58:28
Block: 1151059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113081 RingCT/type: yes/0
Extra: 0103ce414d1040af399ec72852ffa943b0656bb5e10afd21f233b0589ea4f0e5af0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01320923d9d28b96ec682bcb2732e317a8d34d6b873890ec820bbc6cb9c28847 0.600000000000 1636516 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": 1151069, "vin": [ { "gen": { "height": 1151059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01320923d9d28b96ec682bcb2732e317a8d34d6b873890ec820bbc6cb9c28847" } } ], "extra": [ 1, 3, 206, 65, 77, 16, 64, 175, 57, 158, 199, 40, 82, 255, 169, 67, 176, 101, 107, 181, 225, 10, 253, 33, 242, 51, 176, 88, 158, 164, 240, 229, 175, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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