Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f026b02bc420abb6bbe375faf84e5509e06c138d77f520341979c33fb29077c0

Tx prefix hash: 47685d92f16569b2200f046523201d8eb1d9204a74c7313a46bade1e94c1728e
Tx public key: 6e87a792b6cfaeaddf471fa7071ae2e80956a8011ca7c0775329815ae5eb4d3a
Timestamp: 1581231632 Timestamp [UCT]: 2020-02-09 07:00:32 Age [y:d:h:m:s]: 05:269:23:05:54
Block: 61090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1343504 RingCT/type: yes/0
Extra: 016e87a792b6cfaeaddf471fa7071ae2e80956a8011ca7c0775329815ae5eb4d3a0211000000104943cd9f000000000000000000

1 output(s) for total of 385.154918774000 dcy

stealth address amount amount idx
00: 8b9f474a1d09b293a0fa5af9a08e97e4ea150e6836873ae57e268a5f00b87aca 385.154918774000 112591 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": 61100, "vin": [ { "gen": { "height": 61090 } } ], "vout": [ { "amount": 385154918774, "target": { "key": "8b9f474a1d09b293a0fa5af9a08e97e4ea150e6836873ae57e268a5f00b87aca" } } ], "extra": [ 1, 110, 135, 167, 146, 182, 207, 174, 173, 223, 71, 31, 167, 7, 26, 226, 232, 9, 86, 168, 1, 28, 167, 192, 119, 83, 41, 129, 90, 229, 235, 77, 58, 2, 17, 0, 0, 0, 16, 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