Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bc24b24ccb2e1bd6fffd12dc61d09303b1f1cfbb80ade5deec365e83ffd9245

Tx prefix hash: 7edcc1142dc06a82683483f0d76792f819067b78d197578f556512af39b992ea
Tx public key: 16c906d316be373a03fbcaf7258b38bbe9a7529efa5f03b0d928a769681c8cce
Timestamp: 1699398560 Timestamp [UCT]: 2023-11-07 23:09:20 Age [y:d:h:m:s]: 01:152:20:51:10
Block: 886768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370437 RingCT/type: yes/0
Extra: 0116c906d316be373a03fbcaf7258b38bbe9a7529efa5f03b0d928a769681c8cce02110000000a4b8f5122000000000000000000

1 output(s) for total of 0.707570151000 dcy

stealth address amount amount idx
00: efb185617cad915992f1934b0bcb02fa326062c56f2a7786fa863a6ba85c416c 0.707570151000 1342611 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": 886778, "vin": [ { "gen": { "height": 886768 } } ], "vout": [ { "amount": 707570151, "target": { "key": "efb185617cad915992f1934b0bcb02fa326062c56f2a7786fa863a6ba85c416c" } } ], "extra": [ 1, 22, 201, 6, 211, 22, 190, 55, 58, 3, 251, 202, 247, 37, 139, 56, 187, 233, 167, 82, 158, 250, 95, 3, 176, 217, 40, 167, 105, 104, 28, 140, 206, 2, 17, 0, 0, 0, 10, 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