Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22b4549b53c4488cfbfd7b63c98352457afe5bfbad1c514d323a9a7675185659

Tx prefix hash: 1205ad459ac9da3d4f39848e1a9d5dc3f2f80a3669394ffe7958ade8fde1dd24
Tx public key: 2bef904b936e82100f783933a8f75f8d6f65ed6422bf1b264f5aa4d9563f204e
Timestamp: 1660172296 Timestamp [UCT]: 2022-08-10 22:58:16 Age [y:d:h:m:s]: 02:158:20:49:06
Block: 563104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 634993 RingCT/type: yes/0
Extra: 012bef904b936e82100f783933a8f75f8d6f65ed6422bf1b264f5aa4d9563f204e021100000001ec6d1a1a000000000000000000

1 output(s) for total of 8.359933166000 dcy

stealth address amount amount idx
00: cf6725fdf5e4418b3159d19a3aef1e9a6345d1a4f70b412a7a9d8196a2716e7b 8.359933166000 995866 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": 563114, "vin": [ { "gen": { "height": 563104 } } ], "vout": [ { "amount": 8359933166, "target": { "key": "cf6725fdf5e4418b3159d19a3aef1e9a6345d1a4f70b412a7a9d8196a2716e7b" } } ], "extra": [ 1, 43, 239, 144, 75, 147, 110, 130, 16, 15, 120, 57, 51, 168, 247, 95, 141, 111, 101, 237, 100, 34, 191, 27, 38, 79, 90, 164, 217, 86, 63, 32, 78, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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