Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f6c127e5b252b562150c53833064328c47c1d8d73ac4b57aa0938b82c8c88a4

Tx prefix hash: 06f242f2dc91073a4d1159a66948c1e28e74a7b3d1e59e8da566d973d153b129
Tx public key: fde9c9b2b856df3d39d921e7decfba4f09a3bf66798a4ec6eedf30b47db6d54c
Timestamp: 1706282487 Timestamp [UCT]: 2024-01-26 15:21:27 Age [y:d:h:m:s]: 01:293:05:18:56
Block: 943801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468392 RingCT/type: yes/0
Extra: 01fde9c9b2b856df3d39d921e7decfba4f09a3bf66798a4ec6eedf30b47db6d54c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cafcf83dbb64edf67bdb4f0478e0a58027c9a034829050341fea4bfce62cf8d 0.600000000000 1402027 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": 943811, "vin": [ { "gen": { "height": 943801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cafcf83dbb64edf67bdb4f0478e0a58027c9a034829050341fea4bfce62cf8d" } } ], "extra": [ 1, 253, 233, 201, 178, 184, 86, 223, 61, 57, 217, 33, 231, 222, 207, 186, 79, 9, 163, 191, 102, 121, 138, 78, 198, 238, 223, 48, 180, 125, 182, 213, 76, 2, 17, 0, 0, 0, 4, 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