Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd6fd6bf33b8a4550b16ecf91aab586bdaceb4e247795995fa9fc2e873593172

Tx prefix hash: 018a692e03f70962f4cffb74085a19add6c1ede19382fb44d25d7851f8aedd1f
Tx public key: ebbbae932a0f8837e6a21af8fcd219f68e6471f86a0b98d35d6236a5af5d993e
Timestamp: 1620006879 Timestamp [UCT]: 2021-05-03 01:54:39 Age [y:d:h:m:s]: 03:281:23:43:44
Block: 252820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 961645 RingCT/type: yes/0
Extra: 01ebbbae932a0f8837e6a21af8fcd219f68e6471f86a0b98d35d6236a5af5d993e021100000025cc643473000000000000000000

1 output(s) for total of 89.191905213000 dcy

stealth address amount amount idx
00: fc1fe548f741eae3ff2bd3399d694ac9fa883d2ad41d11e2b9b02e8e0db906f5 89.191905213000 530823 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": 252830, "vin": [ { "gen": { "height": 252820 } } ], "vout": [ { "amount": 89191905213, "target": { "key": "fc1fe548f741eae3ff2bd3399d694ac9fa883d2ad41d11e2b9b02e8e0db906f5" } } ], "extra": [ 1, 235, 187, 174, 147, 42, 15, 136, 55, 230, 162, 26, 248, 252, 210, 25, 246, 142, 100, 113, 248, 106, 11, 152, 211, 93, 98, 54, 165, 175, 93, 153, 62, 2, 17, 0, 0, 0, 37, 204, 100, 52, 115, 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