Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7c5c1c2469dc69ba26c8b956a7856a394aebaa8c432b8c7c2b1c13b8e654f07

Tx prefix hash: 6d029e0c41d625be7fb546abb6ba396d6a15aa3b965ee0776875edc1447f93d5
Tx public key: 24cbd02298e59b793dae7a49847db31f3c77989fa250afe5aea8f0bf50da08af
Timestamp: 1657288253 Timestamp [UCT]: 2022-07-08 13:50:53 Age [y:d:h:m:s]: 02:278:20:54:04
Block: 539361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 720427 RingCT/type: yes/0
Extra: 0124cbd02298e59b793dae7a49847db31f3c77989fa250afe5aea8f0bf50da08af021100000014bf7ee4e7000000000000000000

1 output(s) for total of 10.020127679000 dcy

stealth address amount amount idx
00: 42350fd2d9ba883d86d77fff388de823d75c3f03a83df633a3b6e1e1b58009c5 10.020127679000 969456 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": 539371, "vin": [ { "gen": { "height": 539361 } } ], "vout": [ { "amount": 10020127679, "target": { "key": "42350fd2d9ba883d86d77fff388de823d75c3f03a83df633a3b6e1e1b58009c5" } } ], "extra": [ 1, 36, 203, 208, 34, 152, 229, 155, 121, 61, 174, 122, 73, 132, 125, 179, 31, 60, 119, 152, 159, 162, 80, 175, 229, 174, 168, 240, 191, 80, 218, 8, 175, 2, 17, 0, 0, 0, 20, 191, 126, 228, 231, 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