Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8b205b55326ae0428f7ac36728976053a2783bb95331d83ab12b7d195a93340

Tx prefix hash: 70fcc94031759dc6ff7c41034639e399cc749ad4acbde8c245ef5501b78bdfc1
Tx public key: a57d114cb9a718d7ace5effbcb66e61fc2d06a7dc3377c425cd3b6212ab5ef4c
Timestamp: 1644940760 Timestamp [UCT]: 2022-02-15 15:59:20 Age [y:d:h:m:s]: 03:027:14:57:49
Block: 439250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 799700 RingCT/type: yes/0
Extra: 01a57d114cb9a718d7ace5effbcb66e61fc2d06a7dc3377c425cd3b6212ab5ef4c021100000002d3fcec30000000000000000000

1 output(s) for total of 21.507142032000 dcy

stealth address amount amount idx
00: b38a829d2f1e9f88cdcc4828f51f31680bead4fdfafd19c79f89ddeb5ca4a018 21.507142032000 851311 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": 439260, "vin": [ { "gen": { "height": 439250 } } ], "vout": [ { "amount": 21507142032, "target": { "key": "b38a829d2f1e9f88cdcc4828f51f31680bead4fdfafd19c79f89ddeb5ca4a018" } } ], "extra": [ 1, 165, 125, 17, 76, 185, 167, 24, 215, 172, 229, 239, 251, 203, 102, 230, 31, 194, 208, 106, 125, 195, 55, 124, 66, 92, 211, 182, 33, 42, 181, 239, 76, 2, 17, 0, 0, 0, 2, 211, 252, 236, 48, 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