Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78cd752c66d6006e766d535b9df65177ba3922de351dc7877195cb2af09f533f

Tx prefix hash: 4fa1a46206f57948bf8df5e28fa24a36d1044c7e24888a89895c5f7df833dcbb
Tx public key: c02c588ea8c39a1d239a72bae46e48fd1e0373f9c5be2c0494bb565f6d4ca1ac
Timestamp: 1582036156 Timestamp [UCT]: 2020-02-18 14:29:16 Age [y:d:h:m:s]: 04:261:14:23:37
Block: 67563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1079290 RingCT/type: yes/0
Extra: 01c02c588ea8c39a1d239a72bae46e48fd1e0373f9c5be2c0494bb565f6d4ca1ac021100000003026b59f3000000000000000000

1 output(s) for total of 366.552800168000 dcy

stealth address amount amount idx
00: 244d9e8ff2e27b39d85535db2c64059e8277ea3b18b8e8e18eb887486f7078fb 366.552800168000 124434 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": 67573, "vin": [ { "gen": { "height": 67563 } } ], "vout": [ { "amount": 366552800168, "target": { "key": "244d9e8ff2e27b39d85535db2c64059e8277ea3b18b8e8e18eb887486f7078fb" } } ], "extra": [ 1, 192, 44, 88, 142, 168, 195, 154, 29, 35, 154, 114, 186, 228, 110, 72, 253, 30, 3, 115, 249, 197, 190, 44, 4, 148, 187, 86, 95, 109, 76, 161, 172, 2, 17, 0, 0, 0, 3, 2, 107, 89, 243, 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