Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c2b8bb18f5652767628a081219677f1daad6ef9f774a20d920b5d01571ef940

Tx prefix hash: 7994e23df762b4d9be9b7402d20423b6299729450704a7548465cae9b7638451
Tx public key: b5c0e543c35f550920a00ffa34a0b4dc25fd6a5585bb5fb1402205e94455e2e8
Timestamp: 1658351027 Timestamp [UCT]: 2022-07-20 21:03:47 Age [y:d:h:m:s]: 03:103:13:16:23
Block: 548095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 853776 RingCT/type: yes/0
Extra: 01b5c0e543c35f550920a00ffa34a0b4dc25fd6a5585bb5fb1402205e94455e2e8021100000026d3fcec30000000000000000000

1 output(s) for total of 9.374192661000 dcy

stealth address amount amount idx
00: 426a5e0ca657f7f7ccfc75b3f5b6a15a1cd4e8d99e8d4626d8a1e3ca7ba6da3f 9.374192661000 979312 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": 548105, "vin": [ { "gen": { "height": 548095 } } ], "vout": [ { "amount": 9374192661, "target": { "key": "426a5e0ca657f7f7ccfc75b3f5b6a15a1cd4e8d99e8d4626d8a1e3ca7ba6da3f" } } ], "extra": [ 1, 181, 192, 229, 67, 195, 95, 85, 9, 32, 160, 15, 250, 52, 160, 180, 220, 37, 253, 106, 85, 133, 187, 95, 177, 64, 34, 5, 233, 68, 85, 226, 232, 2, 17, 0, 0, 0, 38, 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