Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20cf2b0c2ceca745e7139c0f829eb30e483dd0a6c0efa801655fedda50d6bd9d

Tx prefix hash: d53bd6a66c34bd12e8538905fba27a0a1a2f9834786bc60ec59210d5e16c870c
Tx public key: 0f67f9569dbbcd9eb28e2cea64dbea677ab2629550e920527af088fc2c8c0a72
Timestamp: 1580859347 Timestamp [UCT]: 2020-02-04 23:35:47 Age [y:d:h:m:s]: 04:328:14:33:40
Block: 58672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126381 RingCT/type: yes/0
Extra: 010f67f9569dbbcd9eb28e2cea64dbea677ab2629550e920527af088fc2c8c0a720211000000184943cd9f000000000000000000

1 output(s) for total of 392.293515444000 dcy

stealth address amount amount idx
00: d9a9c4c0862b9a472bc1aa30e6a8325923f1492d3d138916061a91b7afe523dd 392.293515444000 108436 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 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": 58682, "vin": [ { "gen": { "height": 58672 } } ], "vout": [ { "amount": 392293515444, "target": { "key": "d9a9c4c0862b9a472bc1aa30e6a8325923f1492d3d138916061a91b7afe523dd" } } ], "extra": [ 1, 15, 103, 249, 86, 157, 187, 205, 158, 178, 142, 44, 234, 100, 219, 234, 103, 122, 178, 98, 149, 80, 233, 32, 82, 122, 240, 136, 252, 44, 140, 10, 114, 2, 17, 0, 0, 0, 24, 73, 67, 205, 159, 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