Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f953a7c3a0617f763c7d9f63358586328714a14c115ccc3e526dc7a1b82d527

Tx prefix hash: 0b9e83a5cf2881cbe92df67ebf09ed29e0ab425917eb8817f91d3cb5a5715a86
Tx public key: 2f358f77678ea2b7e05271845a84098187f0bdc85f367b44790caeaae0469423
Timestamp: 1578639954 Timestamp [UCT]: 2020-01-10 07:05:54 Age [y:d:h:m:s]: 05:027:23:51:33
Block: 42306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170163 RingCT/type: yes/0
Extra: 012f358f77678ea2b7e05271845a84098187f0bdc85f367b44790caeaae04694230211000000124943cd9f000000000000000000

1 output(s) for total of 444.450607546000 dcy

stealth address amount amount idx
00: e361cffbd411e96f5faa8e97aeb957b3c389d1cad2b1705c0acfdc93e5aa7dc3 444.450607546000 76149 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": 42316, "vin": [ { "gen": { "height": 42306 } } ], "vout": [ { "amount": 444450607546, "target": { "key": "e361cffbd411e96f5faa8e97aeb957b3c389d1cad2b1705c0acfdc93e5aa7dc3" } } ], "extra": [ 1, 47, 53, 143, 119, 103, 142, 162, 183, 224, 82, 113, 132, 90, 132, 9, 129, 135, 240, 189, 200, 95, 54, 123, 68, 121, 12, 174, 170, 224, 70, 148, 35, 2, 17, 0, 0, 0, 18, 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