Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f056dfa4b183e9499595d23cd2348660c9ac3b28a338a786feb5bd1dd2e83c85

Tx prefix hash: 426f6c8b2e0a7b8bc763ecf8310a755811315edbc01827d58c8206bc3b916b94
Tx public key: 77c7a0b854dc858e86d47ad489ac286cd2f2e56fbd8d1b043a6f526dee8cf187
Timestamp: 1581848635 Timestamp [UCT]: 2020-02-16 10:23:55 Age [y:d:h:m:s]: 04:351:14:40:31
Block: 66226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143208 RingCT/type: yes/0
Extra: 0177c7a0b854dc858e86d47ad489ac286cd2f2e56fbd8d1b043a6f526dee8cf1870211000000018a2ee0d9000000000000000000

1 output(s) for total of 370.310971549000 dcy

stealth address amount amount idx
00: 252b0e983fdea82d0ad9502a932c5a17081253b8162fd7e770d5ce2ffd5f07ce 370.310971549000 121975 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": 66236, "vin": [ { "gen": { "height": 66226 } } ], "vout": [ { "amount": 370310971549, "target": { "key": "252b0e983fdea82d0ad9502a932c5a17081253b8162fd7e770d5ce2ffd5f07ce" } } ], "extra": [ 1, 119, 199, 160, 184, 84, 220, 133, 142, 134, 212, 122, 212, 137, 172, 40, 108, 210, 242, 229, 111, 189, 141, 27, 4, 58, 111, 82, 109, 238, 140, 241, 135, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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