Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c2975c0e37ce4f2a18a81ee11105a5706b83ffde58f2c4f5c291bc825f17462

Tx prefix hash: 776e7059760ab09af4aa0fb65273d6c9db1cdc2c232d8e75aa425a949c0aff7d
Tx public key: 23f2f3ace265ec1e44990e2591e1f03fde8fa1dc3f3c943954d45befe1313409
Timestamp: 1659959734 Timestamp [UCT]: 2022-08-08 11:55:34 Age [y:d:h:m:s]: 02:191:23:22:03
Block: 561393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 658342 RingCT/type: yes/0
Extra: 0123f2f3ace265ec1e44990e2591e1f03fde8fa1dc3f3c943954d45befe131340902110000000124ffc81c000000000000000000

1 output(s) for total of 8.469778663000 dcy

stealth address amount amount idx
00: 672a80ee037a7fe326aefafa7c871d616033f065cbf446ac06163cf3e707a218 8.469778663000 993705 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": 561403, "vin": [ { "gen": { "height": 561393 } } ], "vout": [ { "amount": 8469778663, "target": { "key": "672a80ee037a7fe326aefafa7c871d616033f065cbf446ac06163cf3e707a218" } } ], "extra": [ 1, 35, 242, 243, 172, 226, 101, 236, 30, 68, 153, 14, 37, 145, 225, 240, 63, 222, 143, 161, 220, 63, 60, 148, 57, 84, 212, 91, 239, 225, 49, 52, 9, 2, 17, 0, 0, 0, 1, 36, 255, 200, 28, 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