Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 103f6cfe9ca546fb2564ab29a40ab0c8a10a693c8bdb5cd81de38694c778bb40

Tx prefix hash: a1c2195d9e71d941caea08c78860d21a8baa7997b2042258652ef1ade2de0688
Tx public key: 4462043e2fc91ed39ad4f9555698d3cff160f35ac31c904e524d1be4c7f76d4c
Timestamp: 1708578572 Timestamp [UCT]: 2024-02-22 05:09:32 Age [y:d:h:m:s]: 01:021:10:52:42
Block: 962861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276371 RingCT/type: yes/0
Extra: 014462043e2fc91ed39ad4f9555698d3cff160f35ac31c904e524d1be4c7f76d4c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1d9957ff445fd2ea4b463a859bd2cdd7b2fe4c48be1af77cb9b8807de84838f 0.600000000000 1422548 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": 962871, "vin": [ { "gen": { "height": 962861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1d9957ff445fd2ea4b463a859bd2cdd7b2fe4c48be1af77cb9b8807de84838f" } } ], "extra": [ 1, 68, 98, 4, 62, 47, 201, 30, 211, 154, 212, 249, 85, 86, 152, 211, 207, 241, 96, 243, 90, 195, 28, 144, 78, 82, 77, 27, 228, 199, 247, 109, 76, 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