Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7f03c66d542b613ef917efa1dd19e89b085f4da8fb97a1eddc79e62ec0e7542

Tx prefix hash: b8fd61322711b14745689b15facfdc52a353d76231855c9a0173d74068279e8a
Tx public key: 10000ca4e7479e0bcc9169643f6cc0a21654961a8156a1de18e007bf21b8a8df
Timestamp: 1583851997 Timestamp [UCT]: 2020-03-10 14:53:17 Age [y:d:h:m:s]: 04:304:22:30:31
Block: 79822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113087 RingCT/type: yes/0
Extra: 0110000ca4e7479e0bcc9169643f6cc0a21654961a8156a1de18e007bf21b8a8df021100000007203e3db0000000000000000000

1 output(s) for total of 333.823855347000 dcy

stealth address amount amount idx
00: 691b30becd4eea86e276c9895e08d3eab1963c05a2f3d32d044d6925d75ff9e6 333.823855347000 146050 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": 79832, "vin": [ { "gen": { "height": 79822 } } ], "vout": [ { "amount": 333823855347, "target": { "key": "691b30becd4eea86e276c9895e08d3eab1963c05a2f3d32d044d6925d75ff9e6" } } ], "extra": [ 1, 16, 0, 12, 164, 231, 71, 158, 11, 204, 145, 105, 100, 63, 108, 192, 162, 22, 84, 150, 26, 129, 86, 161, 222, 24, 224, 7, 191, 33, 184, 168, 223, 2, 17, 0, 0, 0, 7, 32, 62, 61, 176, 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