Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7b4008545168d422095613de117b1cbe892f19440578ba4ffd327f4847bcf72

Tx prefix hash: 588b43eea0ee98c8962f5e9b69176496aa0d90a0141231f9b4e6161ebf4d346f
Tx public key: 9df4617182538bb408f5e67550e703a5e823a69d8bd31cf60eef6ebd4639d692
Timestamp: 1708611851 Timestamp [UCT]: 2024-02-22 14:24:11 Age [y:d:h:m:s]: 01:271:17:54:52
Block: 963144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452969 RingCT/type: yes/0
Extra: 019df4617182538bb408f5e67550e703a5e823a69d8bd31cf60eef6ebd4639d69202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a4a6d7b239a551d954e4918ce003b761fa9b4d5f29cc0ef8196c2c2099a02cb 0.600000000000 1422843 of 15

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": 963154, "vin": [ { "gen": { "height": 963144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a4a6d7b239a551d954e4918ce003b761fa9b4d5f29cc0ef8196c2c2099a02cb" } } ], "extra": [ 1, 157, 244, 97, 113, 130, 83, 139, 180, 8, 245, 230, 117, 80, 231, 3, 165, 232, 35, 166, 157, 139, 211, 28, 246, 14, 239, 110, 189, 70, 57, 214, 146, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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