Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2279c1f988d49dc8967b80344c9b838678f075711c6d89340e742270bbbdae5

Tx prefix hash: fec540404ef6e52b1e33d65de8fa4841202d686e3b408305a0d189a332f067c8
Tx public key: df57fe6b4763421f6cb4b3cea60dc336be8e690cabd63cfc129f3f3cbd06dfa9
Timestamp: 1694338154 Timestamp [UCT]: 2023-09-10 09:29:14 Age [y:d:h:m:s]: 01:205:17:32:49
Block: 844985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408131 RingCT/type: yes/0
Extra: 01df57fe6b4763421f6cb4b3cea60dc336be8e690cabd63cfc129f3f3cbd06dfa90211000000054b8f5122000000000000000000

1 output(s) for total of 0.973226642000 dcy

stealth address amount amount idx
00: 38d524c71b03d1f9a079a1bdb3790f9db4179664b5217b9bf638280707e169ea 0.973226642000 1298331 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": 844995, "vin": [ { "gen": { "height": 844985 } } ], "vout": [ { "amount": 973226642, "target": { "key": "38d524c71b03d1f9a079a1bdb3790f9db4179664b5217b9bf638280707e169ea" } } ], "extra": [ 1, 223, 87, 254, 107, 71, 99, 66, 31, 108, 180, 179, 206, 166, 13, 195, 54, 190, 142, 105, 12, 171, 214, 60, 252, 18, 159, 63, 60, 189, 6, 223, 169, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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